AI agents call convert_coordinates to retrieve information from Leaflet without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs pure data transformation and validation — converting coordinate formats and checking their validity. It has no side effects, does not modify any external state, and only processes input data to produce converted output. This is a classic Read/compute operation with minimal blast radius.
From the tool's definition Convert between different coordinate formats (decimal degrees, DMS, various notations) and validate coordinates
Attacks that exploit this kind of access
Convert between different coordinate formats (decimal degrees, DMS, various notations) and validate coordinates. It is categorised as a Read tool in the Leaflet MCP Server, which means it retrieves data without modifying state.
Register the Leaflet MCP server in PolicyLayer and add a rule for convert_coordinates: 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 Leaflet. Nothing to install.
convert_coordinates 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 convert_coordinates 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 convert_coordinates. 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.
convert_coordinates is provided by the Leaflet MCP server (philgebauer/leaflet-mcp-server). 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 →