List all saved locations. Use this when a user wants to see their saved locations or asks "what locations do I have saved?" or "show my saved places". Returns all saved locations with their aliases, names, coordinates, and other metadata. Helpful for reminding users what location names they can u...
AI agents call list_saved_locations to retrieve information from Weather Data 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 and queries stored location data without creating, modifying, deleting, or executing any external operations. It is a pure read operation that returns user preferences/metadata. The data retrieved is non-sensitive weather location information, posing minimal risk if misused by an AI agent.
From the tool's definition The tool description states it 'List[s] all saved locations' and 'Returns all saved locations with their aliases, names, coordinates, and other metadata.' The action is retrieval-only with no modification or side effects.
Attacks that exploit this kind of access
List all saved locations. Use this when a user wants to see their saved locations or asks "what locations do I have saved?" or "show my saved places". Returns all saved locations with their aliases, names, coordinates, and other metadata. Helpful for reminding users what location names they can use with weather tools. It is categorised as a Read tool in the Weather Data MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Weather Data MCP Server MCP server in PolicyLayer and add a rule for list_saved_locations: 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.
list_saved_locations 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 list_saved_locations 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 list_saved_locations. 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.
list_saved_locations 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 →