get-directions

Get directions between two points with distance, duration, and turn-by-turn steps.

SERVERRendezvous SOURCErendezvous-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade A, identity unverified Pull the record →

This record as markdown: /tools/dev-forgesworn-rendezvous-mcp/get-directions.md

WHAT IT DOES

What get-directions does on Rendezvous

AI agents call get-directions to retrieve information from Rendezvous without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get-directions is rated Low

This tool retrieves directional data (distance, duration, turn-by-turn steps) between two points. It is purely informational with no side effects—it does not create, modify, delete, or execute operations. It falls clearly into the Read category as a data retrieval function.

From the tool's definition Tool name 'get-directions' and description 'Get directions between two points with distance, duration, and turn-by-turn steps' indicate a read-only query operation that retrieves routing information without modifying, deleting, or executing external commands.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get-directions safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Rendezvous, 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 Allowed

get-directions is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get-directions": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Rendezvous, apply this rule, and every get-directions call is checked against it from then on.

FAQ

Questions about get-directions

What does the get-directions tool do? +

Get directions between two points with distance, duration, and turn-by-turn steps. It is categorised as a Read tool in the Rendezvous MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get-directions? +

Register the Rendezvous 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 Rendezvous. 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 Rendezvous MCP server (rendezvous-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Rendezvous, and thousands of servers like it.

This server

All 5 Rendezvous tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →