Lista todas as cobranças criadas no Abacate Pay
AI agents call listBillings to retrieve information from Abacatepay without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays billing data without creating, modifying, deleting, or executing any operations. It is a pure read operation on existing billing records. The low severity reflects minimal risk even if misused by an agent, as it only exposes billing information retrieval.
From the tool's definition Tool name 'listBillings' and description 'Lista todas as cobranças criadas no Abacate Pay' (Lists all billings created in Abacate Pay) indicate a query/list operation with no side effects.
Attacks that exploit this kind of access
Lista todas as cobranças criadas no Abacate Pay. It is categorised as a Read tool in the Abacatepay MCP Server, which means it retrieves data without modifying state.
Register the Abacatepay MCP server in PolicyLayer and add a rule for listBillings: 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.
listBillings is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the listBillings 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 listBillings. 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.
listBillings 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 →