corrosion_query_typical_rates
AI agents call corrosion_query_typical_rates to retrieve information from Corrosion Engineering MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name suggests querying reference data (typical corrosion rates), which is a retrieval operation with no side effects. No modification, deletion, code execution, or financial impact is implied.
From the tool's definition Tool name 'corrosion_query_typical_rates' contains 'query', indicating a lookup or retrieval operation. Description is empty, limiting direct evidence, but the sibling tool context shows this server performs calculations and queries on corrosion data without…
Attacks that exploit this kind of access
corrosion_query_typical_rates. It is categorised as a Read tool in the Corrosion Engineering MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Corrosion Engineering MCP Server MCP server in PolicyLayer and add a rule for corrosion_query_typical_rates: 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 Corrosion Engineering MCP Server. Nothing to install.
corrosion_query_typical_rates 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 corrosion_query_typical_rates 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 corrosion_query_typical_rates. 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.
corrosion_query_typical_rates is provided by the Corrosion Engineering MCP Server MCP server (puran-water/corrosion-engineering-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 →