list_checkout_sessions

List checkout sessions with pagination. Returns session details including status, amount, currency, and customer info.

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

What list_checkout_sessions does on Payoza MCP Server

AI agents call list_checkout_sessions 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 list_checkout_sessions needs a policy

This tool retrieves and queries existing checkout session data without creating, modifying, deleting, or executing any side effects. It is purely informational in nature. While the server handles financial transactions, this specific tool only reads payment session metadata. Severity is low because misuse would only expose data visibility, not enable unauthorized financial movements.

From the tool's definition Tool name 'list_checkout_sessions' and description 'List checkout sessions...Returns session details' indicates a retrieval operation with no modification capabilities.

Questions about list_checkout_sessions

What does the list_checkout_sessions tool do? +

List checkout sessions with pagination. Returns session details including status, amount, currency, and customer info. 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 list_checkout_sessions? +

Register the Payoza MCP Server MCP server in PolicyLayer and add a rule for list_checkout_sessions: 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 list_checkout_sessions? +

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

Can I rate-limit list_checkout_sessions? +

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

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

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