prepare_buy_checkout · Sanka MCP Server MCP: Risk & Policy

WHAT IT DOES

What prepare_buy_checkout does on Sanka MCP Server

AI agents use prepare_buy_checkout 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 prepare_buy_checkout needs a policy

The tool prepares checkout infrastructure (URL generation) rather than executing payment or transferring funds, making it Write rather than Financial. However, it sits in the payment flow and could be misused to prepare fraudulent checkouts. Severity is medium because while it creates checkout state, payment completion is blocked and the actual financial transaction requires additional steps.

From the tool's definition Tool name 'prepare_buy_checkout' and description indicates it prepares a checkout URL for a merchant purchase after PO creation. The description explicitly states 'This does not complete payment', confirming no financial transaction is executed.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

prepare_buy_checkout Rate-limited

prepare_buy_checkout 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": {
    "prepare_buy_checkout": {
      "limits": [
        {
          "counter": "prepare_buy_checkout_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 prepare_buy_checkout

What does the prepare_buy_checkout tool do? +

Prepare a manual checkout URL for a Sanka Buy merchant purchase after Purchase Order creation. This does not complete payment. 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 prepare_buy_checkout? +

Register the Sanka MCP Server MCP server in PolicyLayer and add a rule for prepare_buy_checkout: 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 prepare_buy_checkout? +

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

Can I rate-limit prepare_buy_checkout? +

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

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

prepare_buy_checkout 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.