eliminar_draft
Elimina permanentemente um rascunho de venda e os dados associados.
This record as markdown: /tools/rubencodex86-officegest-api-v2-mcp/eliminar-draft.md
What eliminar_draft does on MCP Officegest
AI agents call eliminar_draft to permanently remove resources in MCP Officegest, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why eliminar_draft is rated Critical
The tool permanently deletes a sales draft and all associated data. 'Permanentemente' explicitly indicates irreversibility, and the deletion of associated data increases the blast radius, making this a Destructive action with high severity.
From the tool's definition Elimina permanentemente um rascunho de venda e os dados associados
Attacks that exploit this kind of access
The rule that runs eliminar_draft safely
PolicyLayer is an MCP gateway: it sits between your AI agents and MCP Officegest, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For eliminar_draft, this is the rule to start with:
eliminar_draft 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 MCP Officegest, apply this rule, and every eliminar_draft call is checked against it from then on.
Questions about eliminar_draft
Elimina permanentemente um rascunho de venda e os dados associados. It is categorised as a Destructive tool in the MCP Officegest MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP Officegest MCP server in PolicyLayer and add a rule for eliminar_draft: 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 MCP Officegest. Nothing to install.
eliminar_draft 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 eliminar_draft 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 eliminar_draft. 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.
eliminar_draft is provided by the MCP Officegest MCP server (rubencodex86/officegest-api-v2-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on MCP Officegest, and thousands of servers like it.
Across the catalogue