Get details for a specific saved location. Use this when a user wants to view information about a particular saved location, like "show me details for my home location" or "what are the coordinates for my cabin?".
AI agents call get_saved_location 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
alias | string | Yes | The alias/name of the saved location to retrieve (e.g., "home", "work") |
Parameters from the server's own tool schema.
This tool retrieves stored location metadata without creating, modifying, or deleting data. It has no operational side effects and poses minimal risk even if misused by an agent, as it only surfaces information the user has already saved.
From the tool's definition Tool description states 'Get details for a specific saved location' and usage examples are 'show me details' and 'what are the coordinates' — both retrieval operations with no modification or side effects.
Attacks that exploit this kind of access
Get details for a specific saved location. Use this when a user wants to view information about a particular saved location, like "show me details for my home location" or "what are the coordinates for my cabin?". It is categorised as a Read tool in the Weather Data MCP Server MCP Server, which means it retrieves data without modifying state.
get_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 get_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.
get_saved_location 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_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 get_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.
get_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 →