create_checkout · Creem MCP: Risk & Policy

WHAT IT DOES

What create_checkout does on Creem

AI agents use create_checkout to commit financial operations through Creem — usually the final step of a payment, billing, or trading workflow. A call moves real money.

WHY IT NEEDS A POLICY

Why create_checkout needs a policy

Creating a checkout session initiates a payment flow that will result in a financial transaction when completed. This directly commits financial obligations by setting up the conditions for money movement between customer and merchant.

From the tool's definition Create a checkout session for a product. Returns a checkout URL to redirect customers to.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_checkout Approval-gated

Any call to create_checkout is blocked until a human approves it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_checkout": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}

GATE THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about create_checkout

What does the create_checkout tool do? +

Create a checkout session for a product. Returns a checkout URL to redirect customers to. It is categorised as a Financial tool in the Creem MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

How do I enforce a policy on create_checkout? +

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

What risk level is create_checkout? +

create_checkout is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit create_checkout? +

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

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

create_checkout is provided by the Creem MCP server (selenium39/mcp-server-creem). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.