New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

confirm_buy_order

Record the user-confirmed external merchant order id after manual Sanka Buy checkout.

SERVERSanka MCP Server SOURCEsankahq/sanka-mcp
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/sankahq-sanka-mcp/confirm-buy-order.md

What confirm_buy_order does on Sanka MCP Server

AI agents use confirm_buy_order to create or update resources in Sanka MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sanka MCP Server environment.

Why confirm_buy_order is rated Medium

The tool writes/records a buy order confirmation, which modifies state in the Sanka system by capturing and storing an external merchant order ID. This is a Create/Write operation rather than Destructive (irreversible deletion), Execute (arbitrary code/commands), or Financial (direct money movement).

From the tool's definition Tool description states 'Record the user-confirmed external merchant order id after manual Sanka Buy checkout' — this creates/records a new order confirmation in the system.

Questions about confirm_buy_order

What does the confirm_buy_order tool do? +

Record the user-confirmed external merchant order id after manual Sanka Buy checkout. It is categorised as a Write tool in the Sanka MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on confirm_buy_order? +

Register the Sanka MCP Server MCP server in PolicyLayer and add a rule for confirm_buy_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 Sanka MCP Server. Nothing to install.

What risk level is confirm_buy_order? +

confirm_buy_order is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit confirm_buy_order? +

Yes. Add a rate_limit block to the confirm_buy_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.

How do I block confirm_buy_order completely? +

Set action: deny in the PolicyLayer policy for confirm_buy_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.

What MCP server provides confirm_buy_order? +

confirm_buy_order is provided by the Sanka MCP Server MCP server (sankahq/sanka-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Sanka MCP Server, and thousands of servers like it.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Sanka MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.