Cria um novo cliente no Abacate Pay
AI agents use createCustomer to create or update resources in Abacatepay — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Abacatepay environment.
This tool creates new customer records in a payment processing system (Abacate Pay). While not destructive (reversible), not financial (doesn't move money), and not execute (doesn't run arbitrary code), it is a Write operation that modifies persistent state.
From the tool's definition Tool description states 'Cria um novo cliente' (creates a new customer). The server manages financial operations (billings, payments, PIX QR codes) and customer creation is a write operation that creates new records in a payment processing system.
Attacks that exploit this kind of access
Cria um novo cliente no Abacate Pay. It is categorised as a Write tool in the Abacatepay MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Abacatepay MCP server in PolicyLayer and add a rule for createCustomer: 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 Abacatepay. Nothing to install.
createCustomer is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the createCustomer 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 createCustomer. 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.
createCustomer is provided by the Abacatepay MCP server (juliopeixoto/abacatepay-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 →