Busca um token no Pagar.me pelo tokenId (requer Public Key).
AI agents call pagarme_get_token to retrieve information from Payments MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only query operation that retrieves token information from Pagar.me using a Public Key. It does not create, modify, delete, or execute any financial transactions. The severity is low because token retrieval alone has minimal blast radius—it cannot move funds, execute commands, or irreversibly alter state. The confidence is high because the description clearly indicates a fetch/search operation.
From the tool's definition Tool name 'pagarme_get_token' and description 'Busca um token no Pagar.me pelo tokenId' (searches/fetches a token by ID) indicates retrieval of existing data without modification or side effects.
Attacks that exploit this kind of access
Busca um token no Pagar.me pelo tokenId (requer Public Key). It is categorised as a Read tool in the Payments MCP MCP Server, which means it retrieves data without modifying state.
Register the Payments MCP server in PolicyLayer and add a rule for pagarme_get_token: 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 Payments MCP. Nothing to install.
pagarme_get_token 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 pagarme_get_token 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 pagarme_get_token. 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.
pagarme_get_token is provided by the Payments MCP server (lpillonwp/mcp-payments). 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 →