This record as markdown: /tools/heznpc-airmcp/get-directions.md
What get_directions does on AirMCP
AI agents call get_directions to retrieve information from AirMCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_directions is rated Low
This tool retrieves navigation/direction information from Apple Maps, which is a read-only query operation. The user provides two locations as input and receives directions as output. There is no capability to modify map data, execute arbitrary code, delete information, or commit financial transactions.
From the tool's definition Tool name 'get_directions' and description 'Get directions between two locations in Apple Maps' indicate a query/retrieval operation with no side effects. No data is created, modified, deleted, or financial action taken.
Attacks that exploit this kind of access
The rule that runs get_directions safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AirMCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_directions, this is the rule to start with:
get_directions is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect AirMCP, apply this rule, and every get_directions call is checked against it from then on.
Questions about get_directions
Get directions between two locations in Apple Maps. It is categorised as a Read tool in the AirMCP MCP Server, which means it retrieves data without modifying state.
Register the Air 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 AirMCP. 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 Air MCP server (airmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Air, and thousands of servers like it.
This server
Across the catalogue