Place an order for a pet
AI agents use place_order 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 creates/inserts a new order entity, which is a Write operation. It is not Destructive (the order can be cancelled or modified), not Execute (no arbitrary code/commands), not Financial (it records an order but does not process actual payment or commit financial obligations in the sense of moving money).
From the tool's definition Tool name 'place_order' and description 'Place an order for a pet' indicate creation of a new order record in the system. This is a reversible write operation (orders can typically be modified or cancelled).
Attacks that exploit this kind of access
Place an order for a 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 place_order: 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.
place_order 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 place_order 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 place_order. 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.
place_order 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 →