matar_job_queue

Mata um job ativo (remove-o do registo, marcando-o como finalizado).

SERVERMCP Officegest SOURCErubencodex86/officegest-api-v2-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/rubencodex86-officegest-api-v2-mcp/matar-job-queue.md

WHAT IT DOES

What matar_job_queue does on MCP Officegest

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.

RISK

Why matar_job_queue is rated Critical

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

RECOMMENDED RULE

The rule that runs matar_job_queue 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 matar_job_queue, this is the rule to start with:

matar_job_queue Hidden

matar_job_queue is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "matar_job_queue"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect MCP Officegest, apply this rule, and every matar_job_queue call is checked against it from then on.

FAQ

Questions about matar_job_queue

What does the matar_job_queue tool do? +

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.

How do I enforce a policy on matar_job_queue? +

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.

What risk level is matar_job_queue? +

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.

Can I rate-limit matar_job_queue? +

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.

How do I block matar_job_queue completely? +

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.

What MCP server provides matar_job_queue? +

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.

KEEP EXPLORING

More on MCP Officegest, and thousands of servers like it.

This server

All 306 MCP Officegest tools → Critical-risk tools on this server →

Across the catalogue

delete_cron_job on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →