confirm_buy_order · Sanka MCP Server MCP: Risk & Policy

WHAT IT DOES

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 IT NEEDS A POLICY

Why confirm_buy_order needs a policy

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.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

confirm_buy_order Rate-limited

confirm_buy_order stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "confirm_buy_order": {
      "limits": [
        {
          "counter": "confirm_buy_order_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Sanka MCP Server, so you can run agents against it safely.

FAQ

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.