adaptercloud_scheduler_jobs_execute_now
Trigger a scheduled job to execute immediately (out-of-band).
This record as markdown: /tools/burdenoff-adaptercloud-mcp/adaptercloud-scheduler-jobs-execute-now.md
What adaptercloud_scheduler_jobs_execute_now does on Adaptercloud
AI agents invoke adaptercloud_scheduler_jobs_execute_now to trigger actions in Adaptercloud. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes | Schedule ID |
Parameters from the server's own tool schema.
Why adaptercloud_scheduler_jobs_execute_now is rated High
adaptercloud_scheduler_jobs_execute_now triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Attacks that exploit this kind of access
The rule that runs adaptercloud_scheduler_jobs_execute_now safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Adaptercloud, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For adaptercloud_scheduler_jobs_execute_now, this is the rule to start with:
adaptercloud_scheduler_jobs_execute_now 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Adaptercloud, apply this rule, and every adaptercloud_scheduler_jobs_execute_now call is checked against it from then on.
Questions about adaptercloud_scheduler_jobs_execute_now
Trigger a scheduled job to execute immediately (out-of-band). It is categorised as a Execute tool in the Adaptercloud MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
adaptercloud_scheduler_jobs_execute_now accepts 1 parameter: id. Required: id. The full parameter table on this page comes from the server's own tool schema.
Register the Adaptercloud MCP server in PolicyLayer and add a rule for adaptercloud_scheduler_jobs_execute_now: 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 Adaptercloud. Nothing to install.
adaptercloud_scheduler_jobs_execute_now 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 adaptercloud_scheduler_jobs_execute_now 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 adaptercloud_scheduler_jobs_execute_now. 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.
adaptercloud_scheduler_jobs_execute_now is provided by the Adaptercloud MCP server (@burdenoff/adaptercloud-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Adaptercloud, and thousands of servers like it.
Across the catalogue