Update an existing pet
AI agents use update_pet to create or update resources in Petstore MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Petstore MCP Server environment.
This tool modifies pet records but does not permanently delete them or execute arbitrary code. The action is reversible—updates can be undone by subsequent updates. It falls under the Write category as it creates or modifies data reversibly. Severity is medium because incorrect updates could affect pet records and potentially impact business logic, but the action is not destructive or financial.
From the tool's definition Tool name 'update_pet' and description 'Update an existing pet' indicate modification of existing data in a reversible manner.
Attacks that exploit this kind of access
Update an existing pet. It is categorised as a Write tool in the Petstore MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Petstore MCP Server MCP server in PolicyLayer and add a rule for update_pet: 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 Petstore MCP Server. Nothing to install.
update_pet 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 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. 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 is provided by the Petstore MCP Server MCP server (raghavendraprakash/mcpforrestapis). 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 →