accept_order · Kaspi Merchant MCP: Risk & Policy

WHAT IT DOES

What accept_order does on Kaspi Merchant

AI agents invoke accept_order to trigger actions in Kaspi Merchant. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why accept_order needs a policy

Accepting an order triggers an external operation on the Kaspi Marketplace production system, committing the merchant to fulfilling the order. It is irreversible and creates a binding obligation, making it Execute (with near-Destructive/Financial implications). Since it doesn't directly move money but does trigger an irreversible external business commitment, Execute at high severity is the best fit.

From the tool's definition Accept a Kaspi order (set status to ACCEPTED_BY_MERCHANT). WARNING: This is IRREVERSIBLE! The order will be accepted and you must fulfill it.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

accept_order Rate-limited

accept_order stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "accept_order": {
      "limits": [
        {
          "counter": "accept_order_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about accept_order

What does the accept_order tool do? +

Accept a Kaspi order (set status to ACCEPTED_BY_MERCHANT). WARNING: This is IRREVERSIBLE! The order will be accepted and you must fulfill it. It is categorised as a Execute tool in the Kaspi Merchant MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on accept_order? +

Register the Kaspi Merchant MCP server in PolicyLayer and add a rule for accept_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 Kaspi Merchant. Nothing to install.

What risk level is accept_order? +

accept_order is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit accept_order? +

Yes. Add a rate_limit block to the accept_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 accept_order completely? +

Set action: deny in the PolicyLayer policy for accept_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 accept_order? +

accept_order is provided by the Kaspi Merchant MCP server (theyahia/kaspi-merchant-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.