Update an existing pet
AI agents use update_pet_profile to create or update resources in Rover MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Rover MCP Server environment.
This tool creates or modifies data reversibly—it updates pet profile information without deleting or destroying data. While it could theoretically cause confusion if misused (e.g., changing pet breed or medical info), the action is reversible by performing another update. It does not execute arbitrary code, delete data, or move money.
From the tool's definition Tool name 'update_pet_profile' and description 'Update an existing pet' indicate modification of existing data. The context describes managing pet profiles through the Rover marketplace.
Attacks that exploit this kind of access
Update an existing pet. It is categorised as a Write tool in the Rover MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Rover MCP Server MCP server in PolicyLayer and add a rule for update_pet_profile: 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 Rover MCP Server. Nothing to install.
update_pet_profile 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 update_pet_profile 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 update_pet_profile. 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.
update_pet_profile is provided by the Rover MCP Server MCP server (markswendsen-code/mcp-rover). 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 →