Manually fire a workflow once. Keeper picks up within ~5s. Use to test a workflow without waiting for its natural trigger.
Part of the CTRL server.
Free to start. No card required.
AI agents invoke ctrl_fire_manual to trigger processes or run actions in CTRL. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
ctrl_fire_manual can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. PolicyLayer enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
{
"version": "1",
"default": "deny",
"tools": {
"ctrl_fire_manual": {
"limits": [
{
"counter": "ctrl_fire_manual_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}See the full CTRL policy for all 6 tools.
These attack patterns abuse exactly the kind of access ctrl_fire_manual gives an agent. Each links to the full case and the policy that stops it:
Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Manually fire a workflow once. Keeper picks up within ~5s. Use to test a workflow without waiting for its natural trigger.. It is categorised as a Execute tool in the CTRL MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the CTRL MCP server in PolicyLayer and add a rule for ctrl_fire_manual: 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 CTRL. Nothing to install.
ctrl_fire_manual 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 ctrl_fire_manual 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 ctrl_fire_manual. 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.
ctrl_fire_manual is provided by the CTRL MCP server (https://www.ctrl.build/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 6 CTRL tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.