This is a synthetic example. It shows the delivery shape only. It is not a report about a real repository and does not claim a vulnerability.
Repository
https://github.com/EXAMPLE/agent-server
Snapshot: main @ 0123456789ab
Coverage: 14 prioritized files · 182 KB
Observed authority surfaces
- Tool / action exposure: a registered tool can update external records; a separate administrative action is visible through the MCP surface.
- Network / API egress: one client sends authenticated requests to an external API.
- Credential / identity material: configuration reads an API key from the environment.
- Destructive-action surface: a removal operation appears reachable through a registered tool.
Guardrails observed
- An authentication check appears before the HTTP transport is accepted.
- Input validation is present on the primary mutation tool.
- A confirmation or dry-run guard is not obvious in the bounded sample around the destructive action.
Priority review
- Verify that every mutating tool checks caller authority at the final action, not only when the connection is established.
- Confirm that untrusted tool arguments cannot select arbitrary outbound destinations or forward credential material.
- Add or verify explicit confirmation or dry-run behavior for irreversible actions.
Boundary
This is a static public-source preflight. These are review observations, not vulnerability verdicts. A real finding requires primitive, reachability, privilege, and consequence to be established.