Get CRS best practices for specific topics. Covers surveying in Japan, web mapping, data exchange, coordinate storage, mobile GPS, cross-border data, historical data, GIS integration, precision requirements, and projection selection. Provides recommended practices, common mistakes, and reference ...
AI agents call get_best_practices 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 best practice information about Coordinate Reference Systems. It has no capability to modify, delete, execute code, transfer funds, or trigger external operations. It is purely a read operation that returns reference material and guidance. The low severity reflects that misuse would only result in incorrect information being retrieved, with no harmful side effects on systems or data.
From the tool's definition Tool name 'get_best_practices' and description indicating it 'Provides recommended practices, common mistakes, and reference materials' — purely informational retrieval with no data modification, deletion, or side effects.
Attacks that exploit this kind of access
Get CRS best practices for specific topics. Covers surveying in Japan, web mapping, data exchange, coordinate storage, mobile GPS, cross-border data, historical data, GIS integration, precision requirements, and projection selection. Provides recommended practices, common mistakes, and reference materials. 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_best_practices: 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_best_practices 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_best_practices 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_best_practices. 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_best_practices 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 →