cancel_job
Cancel a pending or running job/operation. Flips it to
This record as markdown: /tools/io-github-bitsandtea-postking-mcp/cancel-job.md
What cancel_job does on Postking Mcp
AI agents call cancel_job to permanently remove resources in Postking Mcp, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why cancel_job is rated Critical
Cancelling a job is an irreversible action: a cancelled job cannot be resumed or undone. The operation permanently terminates a pending or running job/operation, making it destructive in nature. Severity is medium since the blast radius is limited to a single job, though cancelling a scheduled post or publishing operation could have meaningful downstream effects.
From the tool's definition cancel_job — 'Cancel a pending or running job/operation. Flips it to' (description appears truncated)
Attacks that exploit this kind of access
The rule that runs cancel_job safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Postking Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For cancel_job, this is the rule to start with:
cancel_job 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 Postking Mcp, apply this rule, and every cancel_job call is checked against it from then on.
Questions about cancel_job
Cancel a pending or running job/operation. Flips it to. It is categorised as a Destructive tool in the Postking Mcp MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Postking MCP server in PolicyLayer and add a rule for cancel_job: 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 Postking Mcp. Nothing to install.
cancel_job 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 cancel_job 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 cancel_job. 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.
cancel_job is provided by the Postking MCP server (postking-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Postking, and thousands of servers like it.
Across the catalogue