createPixCharge
Cria uma cobrança PIX na ZuckPay e retorna o código copia-e-cola, a imagem do QR Code e o link de checkout hospedado.
This record as markdown: /tools/zuckpay-mcp/createpixcharge.md
What createPixCharge does on Zuckpay
AI agents use createPixCharge to commit financial operations through Zuckpay, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why createPixCharge is rated Critical
createPixCharge moves real money, and an autonomous agent will call it with the same confidence it calls a search tool. A misread instruction or an injected prompt is all it takes to drain an account or blow a budget.
Attacks that exploit this kind of access
The rule that runs createPixCharge safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Zuckpay, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For createPixCharge, this is the rule to start with:
Any call to createPixCharge is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Zuckpay, apply this rule, and every createPixCharge call is checked against it from then on.
Questions about createPixCharge
Cria uma cobrança PIX na ZuckPay e retorna o código copia-e-cola, a imagem do QR Code e o link de checkout hospedado. It is categorised as a Financial tool in the Zuckpay MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Zuckpay MCP server in PolicyLayer and add a rule for createPixCharge: 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 Zuckpay. Nothing to install.
createPixCharge 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 createPixCharge 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 createPixCharge. 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.
createPixCharge is provided by the Zuckpay MCP server (ZuckPay/zuckpay-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Zuckpay, and thousands of servers like it.
Across the catalogue