Analyze dependencies used across all routes
AI agents call analyze_dependencies to retrieve information from FastAPI MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and analyzes dependency information from a FastAPI application. It performs static analysis of the dependency injection hierarchy mentioned in the server description, returning information about dependencies without modifying application state, executing arbitrary code, or affecting the application's behavior.
From the tool's definition Tool description states 'Analyze dependencies used across all routes' - a read-only introspection operation. No modifications, deletions, or executions are described.
Attacks that exploit this kind of access
Analyze dependencies used across all routes. It is categorised as a Read tool in the FastAPI MCP Server MCP Server, which means it retrieves data without modifying state.
Register the FastAPI MCP Server MCP server in PolicyLayer and add a rule for analyze_dependencies: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches FastAPI MCP Server. Nothing to install.
analyze_dependencies is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the analyze_dependencies rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for analyze_dependencies. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
analyze_dependencies is provided by the FastAPI MCP Server MCP server (nabeelshar/fastapi-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →