Force unlock all stuck scraping jobs (jobs that haven\
AI agents invoke force_unlock_stuck_jobs to trigger actions in ZMCPTools. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool forcibly overrides lock states on scraping jobs, which is an administrative execution action that modifies system state. While it could be considered Write, the 'force' nature and potential to affect running jobs (possibly interrupting or corrupting in-progress operations) elevates it to Execute.
From the tool's definition 'Force unlock all stuck scraping jobs (jobs that have been stuck...)' - forcibly modifies job state/locks in the system
Documented attack patterns abuse exactly the kind of access force_unlock_stuck_jobs 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_stuck_jobs:
{
"version": "1",
"default": "deny",
"tools": {
"force_unlock_stuck_jobs": {
"limits": [
{
"counter": "force_unlock_stuck_jobs_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}force_unlock_stuck_jobs stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Force unlock all stuck scraping jobs (jobs that haven\. It is categorised as a Execute tool in the ZMCPTools MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the ZMCPTools MCP server in PolicyLayer and add a rule for force_unlock_stuck_jobs: 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_stuck_jobs is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the force_unlock_stuck_jobs 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_stuck_jobs. 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_stuck_jobs 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.