get_checkout_session

Get a checkout session by ID. Returns full session details including payment status.

Server Payoza MCP Server payoza/mcp
Category Read
Risk class Low
Parameters 00 required

What get_checkout_session does on Payoza MCP Server

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

Why get_checkout_session needs a policy

This tool retrieves payment session information without creating, modifying, deleting, or executing any actions. It is a read-only query operation. While it deals with financial data, the tool itself does not move money or commit financial obligations—it only retrieves session state. Severity is low because reading payment session metadata poses minimal risk compared to tools that actually process or move funds.

From the tool's definition Tool name 'get_checkout_session' and description 'Get a checkout session by ID. Returns full session details' indicate retrieval of existing data with no modification or side effects.

Questions about get_checkout_session

What does the get_checkout_session tool do? +

Get a checkout session by ID. Returns full session details including payment status. It is categorised as a Read tool in the Payoza MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_checkout_session? +

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

What risk level is get_checkout_session? +

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

Can I rate-limit get_checkout_session? +

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

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

get_checkout_session is provided by the Payoza MCP Server MCP server (payoza/mcp). 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.