Get historical track (past positions) for a storm
AI agents call get_storm_track 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 and retrieves historical storm track data from NOAA/NHC archives. It performs a read-only operation with no side effects, no data modification, no code execution, and no destructive actions. The blast radius of misuse is minimal—an AI agent could only retrieve historical weather data that is already publicly available.
From the tool's definition Tool name 'get_storm_track' and description 'Get historical track (past positions) for a storm' indicate retrieval of existing historical data with no modification, creation, deletion, or execution capabilities.
Attacks that exploit this kind of access
Get historical track (past positions) for a storm. 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 get_storm_track: 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.
get_storm_track 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_storm_track 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_storm_track. 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_storm_track 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 →