New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

despezzas_delete_credit_card

Exclui cartão. Exige confirm=true.

SERVERDespezzas SOURCEguipmilek/despezzas-mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/despezzas-mcp/despezzas-delete-credit-card.md

What despezzas_delete_credit_card does on Despezzas

AI agents call despezzas_delete_credit_card to permanently remove resources in Despezzas, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why despezzas_delete_credit_card is rated Critical

Deleting a credit card is an irreversible destructive action that removes financial data. While it is not a direct money movement (Financial category), the destruction of a credit card record—a core financial asset—qualifies as Destructive rather than Write. The confirmation requirement demonstrates the tool developers recognized this as a high-consequence operation.

From the tool's definition Tool name includes 'delete' and description states 'Exclui cartão' (deletes credit card). The requirement for 'confirm=true' indicates irreversible removal of a financial asset.

Questions about despezzas_delete_credit_card

What does the despezzas_delete_credit_card tool do? +

Exclui cartão. Exige confirm=true. It is categorised as a Destructive tool in the Despezzas MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on despezzas_delete_credit_card? +

Register the Despezzas MCP server in PolicyLayer and add a rule for despezzas_delete_credit_card: 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 Despezzas. Nothing to install.

What risk level is despezzas_delete_credit_card? +

despezzas_delete_credit_card is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit despezzas_delete_credit_card? +

Yes. Add a rate_limit block to the despezzas_delete_credit_card 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.

How do I block despezzas_delete_credit_card completely? +

Set action: deny in the PolicyLayer policy for despezzas_delete_credit_card. 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.

What MCP server provides despezzas_delete_credit_card? +

despezzas_delete_credit_card is provided by the Despezzas MCP server (guipmilek/despezzas-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Despezzas, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Despezzas's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.