Create a Khipu terminal session for in-person / POS bank-transfer checkout. Returns a QR/URL the payer scans at the point of sale to pay from their bank app.
AI agents use create_terminal_session to commit financial operations through Mcp Ap2 — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool initiates a real payment session via bank transfer at a point of sale. It directly triggers a financial transaction flow where a payer transfers money from their bank account. Misuse could result in unauthorized payment sessions being created, committing financial obligations or enabling fraudulent charges.
From the tool's definition Create a Khipu terminal session for in-person / POS bank-transfer checkout...to pay from their bank app
Documented attack patterns abuse exactly the kind of access create_terminal_session gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Ap2, and nothing reaches the server without passing your rules. This is the rule we recommend for create_terminal_session:
{
"version": "1",
"default": "deny",
"tools": {
"create_terminal_session": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
}Any call to create_terminal_session is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
Create a Khipu terminal session for in-person / POS bank-transfer checkout. Returns a QR/URL the payer scans at the point of sale to pay from their bank app. It is categorised as a Financial tool in the Mcp Ap2 MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Mcp Ap2 MCP server in PolicyLayer and add a rule for create_terminal_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 Mcp Ap2. Nothing to install.
create_terminal_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_terminal_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_terminal_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_terminal_session is provided by the Mcp Ap2 MCP server (@codespar/mcp-ap2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Ap2, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
1300 Mcp Ap2 tools catalogued and risk-classified — across an index of 43,000+ MCP servers.