despezzas_delete_profile
Exclui um perfil compartilhado próprio. Exige confirm=true.
This record as markdown: /tools/despezzas-mcp/despezzas-delete-profile.md
What despezzas_delete_profile does on Despezzas
AI agents call despezzas_delete_profile 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_profile is rated Critical
This tool permanently deletes a user profile, which is an irreversible destructive action. While it requires confirmation (confirm=true), this is a safety measure that does not change the fundamental destructive nature of the operation. Profile deletion cannot be undone and removes data, fitting squarely into the Destructive category.
From the tool's definition Tool description states 'Exclui um perfil' (deletes a profile) and 'Exige confirm=true' (requires confirmation). The verb 'exclui' (deletes) and the context of profile deletion indicate irreversible data removal.
Attacks that exploit this kind of access
The rule that runs despezzas_delete_profile safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Despezzas, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For despezzas_delete_profile, this is the rule to start with:
despezzas_delete_profile is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Despezzas, apply this rule, and every despezzas_delete_profile call is checked against it from then on.
Questions about despezzas_delete_profile
Exclui um perfil compartilhado próprio. 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.
Register the Despezzas MCP server in PolicyLayer and add a rule for despezzas_delete_profile: 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.
despezzas_delete_profile is a Destructive 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 despezzas_delete_profile 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 despezzas_delete_profile. 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.
despezzas_delete_profile 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.
Across the catalogue