Calculate travel distance and time for multiple origins and destinations
AI agents call maps_distance_matrix to retrieve information from Helm Chart CLI without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves geographical/routing data and returns computed metrics (distance and time). It has no side effects on any system, does not execute arbitrary code, does not modify data, and does not involve financial transactions. It is a read-only operation that queries a mapping/routing service API for informational results.
From the tool's definition The tool calculates travel distance and time, which is a query/retrieval operation with no modification, deletion, or execution of external commands. The description explicitly states 'Calculate' (retrieve metric data) rather than modify, execute, or delete.
Attacks that exploit this kind of access
Calculate travel distance and time for multiple origins and destinations. It is categorised as a Read tool in the Helm Chart CLI MCP Server, which means it retrieves data without modifying state.
Register the Helm Chart CLI MCP server in PolicyLayer and add a rule for maps_distance_matrix: 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 Helm Chart CLI. Nothing to install.
maps_distance_matrix 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 maps_distance_matrix 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 maps_distance_matrix. 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.
maps_distance_matrix is provided by the Helm Chart CLI MCP server (jeff-nasseri/servers). 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 →