Get directions between origin and destination
AI agents call get_directions to retrieve information from Multi-MCPs without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves directional information from Google Maps (based on server context listing Google Maps as an integrated service). It performs a read-only query operation with no side effects, data modification, code execution, or financial implications. The severity is low as misuse would only expose routing data, posing minimal security risk.
From the tool's definition Tool name 'get_directions' and description 'Get directions between origin and destination' indicate a retrieval operation that queries mapping/routing data without modifying any state or triggering external actions.
Attacks that exploit this kind of access
Get directions between origin and destination. It is categorised as a Read tool in the Multi-MCPs MCP Server, which means it retrieves data without modifying state.
Register the Multi-MCPs MCP server in PolicyLayer and add a rule for get_directions: 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 Multi-MCPs. Nothing to install.
get_directions 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_directions 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_directions. 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_directions is provided by the Multi-MCPs MCP server (taylorchen/muti-mcps). 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 →