Query historical hurricane tracks by area and date range
AI agents call search_historical_tracks to retrieve information from Hurricane Tracker MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries a historical dataset (NOAA/NHC hurricane tracks) filtered by geographic area and date range. It retrieves information for analysis without creating, modifying, deleting, or executing any operations. The blast radius of misuse is negligible; an AI agent cannot cause harm by querying historical storm data. This is a straightforward Read operation.
From the tool's definition Tool name contains 'search' and description states 'Query historical hurricane tracks' — both indicate data retrieval with no modifications, deletions, or external operations.
Attacks that exploit this kind of access
Query historical hurricane tracks by area and date range. It is categorised as a Read tool in the Hurricane Tracker MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Hurricane Tracker MCP Server MCP server in PolicyLayer and add a rule for search_historical_tracks: 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 Hurricane Tracker MCP Server. Nothing to install.
search_historical_tracks 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 search_historical_tracks 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 search_historical_tracks. 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.
search_historical_tracks is provided by the Hurricane Tracker MCP Server MCP server (kumaran-is/hurricane-tracker-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 →