place_order
Place an order for a product. Requires a valid badge.
This record as markdown: /tools/a2a-demos/place-order.md
What place_order does on A2a Demos
AI agents use place_order to commit financial operations through A2a Demos, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why place_order is rated Critical
Placing an order is a financial commitment that can result in charges, purchases, or binding contracts. Misuse by an AI agent could result in unauthorized purchases. The 'requires a valid badge' note indicates the server itself recognizes this as a sensitive, authorization-gated action. This falls clearly under Financial as it commits financial obligations.
From the tool's definition 'Place an order for a product' — placing an order commits a financial obligation to purchase goods/services.
Attacks that exploit this kind of access
The rule that runs place_order safely
PolicyLayer is an MCP gateway: it sits between your AI agents and A2a Demos, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For place_order, this is the rule to start with:
Any call to place_order is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect A2a Demos, apply this rule, and every place_order call is checked against it from then on.
Questions about place_order
Place an order for a product. Requires a valid badge. It is categorised as a Financial tool in the A2a Demos MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the A2a Demos 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 A2a Demos. Nothing to install.
place_order is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
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 A2a Demos MCP server (capiscio/a2a-demos). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on A2a Demos, and thousands of servers like it.
Across the catalogue