driving_route_planning
AI agents call driving_route_planning to retrieve information from Amap MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Based on the server context providing route planning services and sibling tools like 'amap_route_subway', 'bicycling_route_planning', and 'public_transit_route_planning', this tool likely queries driving route information from the Amap API. This is a read operation with no side effects. Confidence is reduced due to empty description.
From the tool's definition Tool name 'driving_route_planning' and server context describing route planning services; description is empty.
Attacks that exploit this kind of access
driving_route_planning. It is categorised as a Read tool in the Amap MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Amap MCP Server MCP server in PolicyLayer and add a rule for driving_route_planning: 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 Amap MCP Server. Nothing to install.
driving_route_planning 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 driving_route_planning 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 driving_route_planning. 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.
driving_route_planning is provided by the Amap MCP Server MCP server (qiao101660/gaode_mcp). 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 →