Get detailed information about a specific route
AI agents call get_route_details 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 performs read-only introspection of a FastAPI application's route metadata and configuration. It retrieves and returns structured information about routes (likely including endpoint handlers, HTTP methods, parameters, response models, etc.) with no side effects, data modification, code execution, or destructive operations.
From the tool's definition Tool name is 'get_route_details' and description states it 'Get detailed information about a specific route'. This is a retrieval operation that queries and returns information about FastAPI routes without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
Get detailed information about a specific route. 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 get_route_details: 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.
get_route_details 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 get_route_details 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 get_route_details. 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.
get_route_details 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 →