Save a favorite location for quick access.
AI agents use save_favorite to create or update resources in PyWeatherMCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your PyWeatherMCP environment.
This tool creates or modifies user preference data (favorites list) in a reversible manner. It does not delete data (Destructive), execute arbitrary operations (Execute), involve financial transactions (Financial), or read without side effects (Read). The blast radius of misuse is minimal—an attacker could spam a user's favorites list, but this is easily remedied by clearing or editing the list.
From the tool's definition Tool name 'save_favorite' and description 'Save a favorite location' indicate data creation/modification. The tool stores user preferences in what is presumably a favorites list.
Attacks that exploit this kind of access
Save a favorite location for quick access. It is categorised as a Write tool in the PyWeatherMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the PyWeather MCP server in PolicyLayer and add a rule for save_favorite: 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.
save_favorite is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the save_favorite 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 save_favorite. 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.
save_favorite 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 →