Troubleshoot CRS-related problems. Diagnoses coordinate shifts (cm, m, km scale), area/distance calculation errors, data not displaying, and transformation errors. Identifies causes, provides diagnostic steps, and solutions.
AI agents call troubleshoot to retrieve information from Epsg without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs diagnostic analysis and provides information/recommendations about CRS problems. It reads and analyzes problem descriptions, then returns diagnostic information. There are no side effects, data modifications, code execution, or financial implications — it purely retrieves and synthesizes knowledge about CRS issues.
From the tool's definition Troubleshoot CRS-related problems. Diagnoses coordinate shifts, calculation errors, data not displaying, and transformation errors. Identifies causes, provides diagnostic steps, and solutions.
Attacks that exploit this kind of access
Troubleshoot CRS-related problems. Diagnoses coordinate shifts (cm, m, km scale), area/distance calculation errors, data not displaying, and transformation errors. Identifies causes, provides diagnostic steps, and solutions. It is categorised as a Read tool in the Epsg MCP Server, which means it retrieves data without modifying state.
Register the Epsg MCP server in PolicyLayer and add a rule for troubleshoot: 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 Epsg. Nothing to install.
troubleshoot 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 troubleshoot 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 troubleshoot. 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.
troubleshoot is provided by the Epsg MCP server (shuji-bonji/epsg-mcp). 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 →