stateset_get_checkout
Retrieves a checkout session. Returns cart contents, shipping info, payment details, and order totals including tax and shipping costs.
This record as markdown: /tools/stateset-mcp-server/stateset-get-checkout.md
What stateset_get_checkout does on Stateset
AI agents call stateset_get_checkout to retrieve information from Stateset without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why stateset_get_checkout is rated Low
This tool retrieves checkout data for query purposes only. While it exposes sensitive information (payment details, order totals), it performs no writes, executions, deletions, or financial transactions—it merely fetches and returns existing checkout state. The risk is informational leakage rather than action-based harm, making this a Read operation with low severity.
From the tool's definition Tool name contains 'get' and description states 'Retrieves a checkout session' with no modification or deletion language. Returns data about 'cart contents, shipping info, payment details, and order totals' without side effects.
Attacks that exploit this kind of access
The rule that runs stateset_get_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_get_checkout, this is the rule to start with:
stateset_get_checkout is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Stateset, apply this rule, and every stateset_get_checkout call is checked against it from then on.
Questions about stateset_get_checkout
Retrieves a checkout session. Returns cart contents, shipping info, payment details, and order totals including tax and shipping costs. It is categorised as a Read tool in the Stateset MCP Server, which means it retrieves data without modifying state.
Register the Stateset MCP server in PolicyLayer and add a rule for stateset_get_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_get_checkout is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the stateset_get_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_get_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_get_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.
This server
Across the catalogue