Force trigger a GoodJob cron schedule immediately. Enqueues a new job for the specified cron schedule regardless of its normal schedule. Use cases: - Manually trigger a cron job for testing - Force an immediate run of a periodic job - Re-run a cron job that was missed
AI agents invoke force_trigger_good_job_cron to trigger actions in Playwright Stealth. 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 executes a background job/cron schedule outside its normal timing. It triggers external operations (job execution) whose effects depend on which cron job is targeted. Since cron jobs can have wide-ranging side effects (data processing, notifications, system operations), misuse could have significant blast radius. This is Execute category as it runs/triggers external operations.
From the tool's definition Force trigger a GoodJob cron schedule immediately. Enqueues a new job for the specified cron schedule regardless of its normal schedule.
Documented attack patterns abuse exactly the kind of access force_trigger_good_job_cron gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Playwright Stealth, and nothing reaches the server without passing your rules. This is the rule we recommend for force_trigger_good_job_cron:
{
"version": "1",
"default": "deny",
"tools": {
"force_trigger_good_job_cron": {
"limits": [
{
"counter": "force_trigger_good_job_cron_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}force_trigger_good_job_cron 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 trigger a GoodJob cron schedule immediately. Enqueues a new job for the specified cron schedule regardless of its normal schedule. Use cases: - Manually trigger a cron job for testing - Force an immediate run of a periodic job - Re-run a cron job that was missed. It is categorised as a Execute tool in the Playwright Stealth MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Playwright Stealth MCP server in PolicyLayer and add a rule for force_trigger_good_job_cron: 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 Playwright Stealth. Nothing to install.
force_trigger_good_job_cron 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_trigger_good_job_cron 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_trigger_good_job_cron. 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_trigger_good_job_cron is provided by the Playwright Stealth MCP server (pulsemcp/mcp-servers). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Playwright Stealth, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
68 Playwright Stealth tools catalogued and risk-classified — across an index of 43,000+ MCP servers.