AI agents call get_crs_detail 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 retrieves and queries reference system metadata without side effects. It answers questions about coordinate reference systems but does not create, modify, delete, or execute any operations. The only input is an EPSG code identifier, and outputs are read-only reference data. This is a straightforward Read category tool with minimal security risk.
From the tool's definition Tool name 'get_crs_detail' and description states it 'Get detailed information for a specific EPSG code' with outputs including 'datum, projection method, area of use, accuracy characteristics, and intended use cases.' This is purely informational retrieval…
Attacks that exploit this kind of access
Get detailed information for a specific EPSG code. Includes datum, projection method, area of use, accuracy characteristics, and intended use cases. 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 get_crs_detail: 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.
get_crs_detail 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 get_crs_detail 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 get_crs_detail. 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.
get_crs_detail 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 →