stateset_complete_checkout
Completes the checkout and creates an order. Processes payment and initiates fulfillment. Returns the created order ID.
This record as markdown: /tools/stateset-mcp-server/stateset-complete-checkout.md
What stateset_complete_checkout does on Stateset
AI agents use stateset_complete_checkout to commit financial operations through Stateset, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why stateset_complete_checkout is rated Critical
This tool explicitly processes payment, which constitutes a financial transaction. It also commits to fulfillment, making it irreversible once triggered. As it moves money and creates binding order obligations, Financial is the most severe applicable category.
From the tool's definition Completes the checkout and creates an order. Processes payment and initiates fulfillment.
Attacks that exploit this kind of access
The rule that runs stateset_complete_checkout safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Stateset, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For stateset_complete_checkout, this is the rule to start with:
Any call to stateset_complete_checkout is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Stateset, apply this rule, and every stateset_complete_checkout call is checked against it from then on.
Questions about stateset_complete_checkout
Completes the checkout and creates an order. Processes payment and initiates fulfillment. Returns the created order ID. It is categorised as a Financial tool in the Stateset MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Stateset MCP server in PolicyLayer and add a rule for stateset_complete_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 Stateset. Nothing to install.
stateset_complete_checkout is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the stateset_complete_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.
Set action: deny in the PolicyLayer policy for stateset_complete_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.
stateset_complete_checkout is provided by the Stateset MCP server (stateset/stateset-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Stateset, and thousands of servers like it.
Across the catalogue