get_directions

Get directions between two locations in Apple Maps.

SERVERIconnect SOURCEiconnect-mcp
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-heznpc-iconnect/get-directions.md

What get_directions does on Iconnect

AI agents call get_directions to retrieve information from Iconnect 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 routing/directions information from Apple Maps. It queries existing data and returns results without creating, modifying, deleting, or executing external actions. The operation is non-destructive and has no financial implications. The minimal risk is informational—directions data is typically public or user-consented within Apple's ecosystem.

From the tool's definition Tool name 'get_directions' and description 'Get directions between two locations in Apple Maps' indicate data retrieval with no modification or side effects. The verb 'Get' and the context of querying map directions clearly denote a read-only operation.

Questions about get_directions

What does the get_directions tool do? +

Get directions between two locations in Apple Maps. It is categorised as a Read tool in the Iconnect MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_directions? +

Register the Iconnect 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 Iconnect. Nothing to install.

What risk level is get_directions? +

get_directions is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_directions? +

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.

How do I block get_directions completely? +

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.

What MCP server provides get_directions? +

get_directions is provided by the Iconnect MCP server (iconnect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Iconnect, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Iconnect's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.