force_trigger_good_job_cron · Pulsemcp Cms Admin MCP

WHAT IT DOES

What force_trigger_good_job_cron does on Pulsemcp Cms Admin

AI agents invoke force_trigger_good_job_cron to trigger actions in Pulsemcp Cms Admin. 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.

WHY IT NEEDS A POLICY

Why force_trigger_good_job_cron needs a policy

This tool executes a background job immediately, bypassing its normal schedule. It triggers external operations (job execution) that could have wide-ranging side effects depending on what the cron job does. Since the effects depend on which cron job is triggered and could include data modification, external API calls, or other system operations, this falls squarely in Execute.

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.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

force_trigger_good_job_cron Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "force_trigger_good_job_cron": {
      "limits": [
        {
          "counter": "force_trigger_good_job_cron_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Pulsemcp Cms Admin, so you can run agents against it safely.

FAQ

Questions about force_trigger_good_job_cron

What does the force_trigger_good_job_cron tool do? +

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 Pulsemcp Cms Admin MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on force_trigger_good_job_cron? +

Register the Pulsemcp Cms Admin 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 Pulsemcp Cms Admin. Nothing to install.

What risk level is force_trigger_good_job_cron? +

force_trigger_good_job_cron is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit force_trigger_good_job_cron? +

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.

How do I block force_trigger_good_job_cron completely? +

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.

What MCP server provides force_trigger_good_job_cron? +

force_trigger_good_job_cron is provided by the Pulsemcp Cms Admin MCP server (pulsemcp-cms-admin-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.