Mata um job ativo (remove-o do registo, marcando-o como finalizado).
AI agents call matar_job_queue 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.
The tool 'kills' (matar) an active job and removes it from the registry, marking it as finished. This is an irreversible termination and deletion of a running job record — it cannot be undone once the job is removed and marked finalized. This qualifies as Destructive due to the permanent removal/termination nature of the action.
From the tool's definition Mata um job ativo (remove-o do registo, marcando-o como finalizado)
Attacks that exploit this kind of access
Mata um job ativo (remove-o do registo, marcando-o como finalizado). 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 matar_job_queue: 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.
matar_job_queue 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 matar_job_queue 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 matar_job_queue. 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.
matar_job_queue 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.
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 →