Get coordinate accuracy codes from USGS OGC API
AI agents call get_coordinate_accuracy_codes to retrieve information from USGS Water MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about coordinate accuracy codes from a public USGS API endpoint. It queries and returns reference information only, with no side effects, data modification, code execution, or destructive capabilities. The blast radius of misuse is minimal—an AI agent could only retrieve publicly available taxonomic/reference data about coordinate accuracy classifications.
From the tool's definition Tool name contains 'get', description states 'Get coordinate accuracy codes', which retrieves reference data with no modification or execution capabilities.
Attacks that exploit this kind of access
Get coordinate accuracy codes from USGS OGC API. It is categorised as a Read tool in the USGS Water MCP MCP Server, which means it retrieves data without modifying state.
Register the USGS Water MCP server in PolicyLayer and add a rule for get_coordinate_accuracy_codes: 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 USGS Water MCP. Nothing to install.
get_coordinate_accuracy_codes 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_coordinate_accuracy_codes 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_coordinate_accuracy_codes. 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_coordinate_accuracy_codes is provided by the USGS Water MCP server (pgiffy/usgs-water-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 →