create_checkout_session
AI agents use create_checkout_session to commit financial operations through Aareguru MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
Although the description is empty, the tool name 'create_checkout_session' and its sibling tools ('cancel_checkout_session', 'complete_checkout') form a clear payment/checkout workflow pattern. Creating a checkout session typically initiates a financial transaction, which is the most severe category. Confidence is reduced due to the empty description.
From the tool's definition Tool name 'create_checkout_session' combined with sibling tools 'cancel_checkout_session' and 'complete_checkout' strongly imply a financial checkout/payment flow.
Attacks that exploit this kind of access
create_checkout_session. It is categorised as a Financial tool in the Aareguru MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Aareguru MCP Server MCP server in PolicyLayer and add a rule for create_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 Aareguru MCP Server. Nothing to install.
create_checkout_session 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 create_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.
Set action: deny in the PolicyLayer policy for create_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.
create_checkout_session is provided by the Aareguru MCP Server MCP server (schlpbch/aareguru-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →