Get extreme water levels and exceedance probabilities for a station
AI agents call get_extreme_water_levels to retrieve information from LocalTides MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical or predictive data about water levels from NOAA's public API. It performs no modifications, deletions, code execution, or financial transactions. The data retrieved is informational and read-only, presenting minimal risk regardless of misuse.
From the tool's definition Tool name 'get_extreme_water_levels' and description 'Get extreme water levels and exceedance probabilities' indicate a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
Get extreme water levels and exceedance probabilities for a station. It is categorised as a Read tool in the LocalTides MCP Server MCP Server, which means it retrieves data without modifying state.
Register the LocalTides MCP Server MCP server in PolicyLayer and add a rule for get_extreme_water_levels: 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 LocalTides MCP Server. Nothing to install.
get_extreme_water_levels 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_extreme_water_levels 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_extreme_water_levels. 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_extreme_water_levels is provided by the LocalTides MCP Server MCP server (ryancardin15/noaa-tidesandcurrents-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 →