Get aquifer identification information from USGS OGC API
AI agents call get_aquifer_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 aquifer codes and identification information—a read-only operation that queries public USGS data. There are no side effects, no data modification, no code execution, no irreversible actions, and no financial implications. The blast radius of misuse is minimal; an agent could only retrieve aquifer reference data that is already public. Classification as Read is appropriate.
From the tool's definition Tool name 'get_aquifer_codes' and description 'Get aquifer identification information from USGS OGC API' indicate retrieval of reference/lookup data without modification or execution of external operations.
Attacks that exploit this kind of access
Get aquifer identification information 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_aquifer_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_aquifer_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_aquifer_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_aquifer_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_aquifer_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 →