AI agents call debug_common_issues 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 is a diagnostic/informational tool that helps users understand and resolve issues with their Leaflet maps. It does not create, modify, delete, or execute code—it merely provides guidance and debugging information. The tool is purely advisory and produces no side effects on the system or data. This falls squarely into the Read category with low severity.
From the tool's definition Tool description: 'Get help debugging common Leaflet issues like map not displaying, tiles not loading, or marker icons missing.' The verb 'Get help debugging' and the read-only nature of diagnostic assistance indicate this tool retrieves or queries…
Attacks that exploit this kind of access
Get help debugging common Leaflet issues like map not displaying, tiles not loading, or marker icons missing. 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 debug_common_issues: 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.
debug_common_issues 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 debug_common_issues 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 debug_common_issues. 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.
debug_common_issues 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 →