Comprehensive tool for managing Paddle transactions for containers. Supports creating Paddle transactions, completing transactions, getting payment method transactions, and retrying charges. Use the
AI agents use stape_container_paddle to commit financial operations through Stape MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool directly handles financial operations via the Paddle payment platform: creating transactions (initiating charges), completing transactions (committing payments), managing payment methods, and retrying charges.
From the tool's definition managing Paddle transactions for containers. Supports creating Paddle transactions, completing transactions, getting payment method transactions, and retrying charges
Documented attack patterns abuse exactly the kind of access stape_container_paddle gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Stape MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for stape_container_paddle:
{
"version": "1",
"default": "deny",
"tools": {
"stape_container_paddle": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
} Any call to stape_container_paddle is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
Comprehensive tool for managing Paddle transactions for containers. Supports creating Paddle transactions, completing transactions, getting payment method transactions, and retrying charges. Use the. It is categorised as a Financial tool in the Stape MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Stape MCP Server MCP server in PolicyLayer and add a rule for stape_container_paddle: 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 Stape MCP Server. Nothing to install.
stape_container_paddle 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 stape_container_paddle 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 stape_container_paddle. 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.
stape_container_paddle is provided by the Stape MCP Server MCP server (stape-io/stape-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Stape MCP Server, 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.
18 Stape MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.