Remove a saved location. Use this when a user wants to delete a saved location, like "remove my work location" or "delete the cabin from saved locations".
AI agents call remove_saved_location to permanently remove resources in Weather Data MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
alias | string | Yes | The alias/name of the saved location to remove (e.g., "home", "work") |
Parameters from the server's own tool schema.
This tool permanently deletes a saved location record. Although the data loss is limited in scope (a single location entry) and the impact is non-critical compared to cascading deletions, it is irreversible and therefore falls under the Destructive category.
From the tool's definition The tool name is 'remove_saved_location' and the description states it will 'Remove a saved location' and 'delete a saved location'. The action is irreversible deletion of stored user data.
Attacks that exploit this kind of access
Remove a saved location. Use this when a user wants to delete a saved location, like "remove my work location" or "delete the cabin from saved locations". It is categorised as a Destructive tool in the Weather Data MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
remove_saved_location accepts 1 parameter: alias. Required: alias. The full parameter table on this page comes from the server's own tool schema.
Register the Weather Data MCP Server MCP server in PolicyLayer and add a rule for remove_saved_location: 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 Weather Data MCP Server. Nothing to install.
remove_saved_location 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 remove_saved_location 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 remove_saved_location. 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.
remove_saved_location is provided by the Weather Data MCP Server MCP server (@dangahagan/weather-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 →