Clear all search history (keeps favorites)
AI agents call clear_history to permanently remove resources in PyWeatherMCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes search history records. While the blast radius is limited to user preferences/history rather than critical infrastructure or financial data, the action is irreversible and destructive in nature. Destructive is the correct category as it involves removing data that cannot be recovered.
From the tool's definition Tool name 'clear_history' and description 'Clear all search history' indicate irreversible deletion of user data. The word 'Clear' combined with 'all search history' describes a destructive operation that cannot be undone.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Clear all search history (keeps favorites). It is categorised as a Destructive tool in the PyWeatherMCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the PyWeather MCP server in PolicyLayer and add a rule for clear_history: 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 PyWeatherMCP. Nothing to install.
clear_history is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the clear_history 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 clear_history. 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.
clear_history is provided by the PyWeather MCP server (zerosks471/pyweathermcp). 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 →