get_checkout

Retrieve checkout session details by ID

Server Creem selenium39/mcp-server-creem
Category Read
Risk class Low
Parameters 00 required

What get_checkout does on Creem

AI agents call get_checkout to retrieve information from Creem without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_checkout needs a policy

This is a straightforward read operation that queries checkout session information. The verb 'Retrieve' and the read-only nature of fetching details by ID indicate no side effects or data modification. Severity is low because checkout session metadata retrieval poses minimal risk even if misused by an agent.

From the tool's definition Tool name 'get_checkout' with description 'Retrieve checkout session details by ID' explicitly performs data retrieval with no modification capability.

Questions about get_checkout

What does the get_checkout tool do? +

Retrieve checkout session details by ID. It is categorised as a Read tool in the Creem MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_checkout? +

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

What risk level is get_checkout? +

get_checkout is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_checkout? +

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

How do I block get_checkout completely? +

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

What MCP server provides get_checkout? +

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

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.