Critical Risk →

ucp_checkout_update

ucp_checkout_update

How to control ucp_checkout_update ↓

What ucp_checkout_update does on Ucp

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

Critical Risk

Why ucp_checkout_update needs a policy

Given the server context (shopping, payments, checkout) and sibling tools (checkout_create, checkout_complete), ucp_checkout_update almost certainly modifies an in-progress checkout, which is a financial operation. Updating a checkout could change quantities, payment methods, or pricing, making it financial in nature. Confidence is reduced because the description is empty and no specific behavior is documented.

From the tool's definition Tool name 'ucp_checkout_update' on a server described as enabling AI assistants to 'shop at UCP-enabled merchants through tools for discovery, checkout, discounts, fulfillment, and payment.' Sibling tools include ucp_checkout_complete and ucp_checkout_create,…

Documented attack patterns abuse exactly the kind of access ucp_checkout_update gives an agent:

How to control ucp_checkout_update

PolicyLayer is an MCP gateway — it sits between your AI agents and Ucp, and nothing reaches the server without passing your rules. This is the rule we recommend for ucp_checkout_update:

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

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

  1. Create a free account and register Ucp — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
GATE THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about ucp_checkout_update

What does the ucp_checkout_update tool do? +

ucp_checkout_update. It is categorised as a Financial tool in the Ucp MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

How do I enforce a policy on ucp_checkout_update? +

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

What risk level is ucp_checkout_update? +

ucp_checkout_update 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 ucp_checkout_update? +

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

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

ucp_checkout_update is provided by the Ucp MCP server (nguthrie/ucp-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Ucp tool call.

Start from Ucp, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

5 Ucp tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.