Get detailed turn-by-turn directions between locations.
AI agents call get_directions to retrieve information from ArcGIS Location Services MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries the ArcGIS Location Services API to fetch directions data. It performs a read-only operation that retrieves information without creating, modifying, deleting, or executing side effects. There is no financial impact, no code execution, and no irreversible changes.
From the tool's definition The tool 'get_directions' retrieves and returns turn-by-turn directions between locations. The description uses 'Get', indicating data retrieval with no modification, deletion, or execution of commands.
Attacks that exploit this kind of access
Get detailed turn-by-turn directions between locations. It is categorised as a Read tool in the ArcGIS Location Services MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ArcGIS Location Services MCP Server 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 ArcGIS Location Services MCP Server. 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 ArcGIS Location Services MCP Server MCP server (lwsinclair/arcgis-location-services-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 →