Force unlock a stuck scraping job - useful for debugging and recovery
AI agents call force_unlock_job to permanently remove resources in ZMCPTools — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
An AI agent that decides to call force_unlock_job doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from ZMCPTools is gone — there is no undo for destructive operations.
Documented attack patterns abuse exactly the kind of access force_unlock_job gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ZMCPTools, and nothing reaches the server without passing your rules. This is the rule we recommend for force_unlock_job:
{
"version": "1",
"default": "deny",
"hide": [
"force_unlock_job"
]
}force_unlock_job disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Force unlock a stuck scraping job - useful for debugging and recovery. It is categorised as a Destructive tool in the ZMCPTools MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the ZMCPTools MCP server in PolicyLayer and add a rule for force_unlock_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 ZMCPTools. Nothing to install.
force_unlock_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 force_unlock_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 force_unlock_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.
force_unlock_job is provided by the ZMCPTools MCP server (zachhandley/zmcptools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 70 ZMCPTools tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
70 ZMCPTools tools catalogued and risk-classified — across an index of 42,500+ MCP servers.