AI agents invoke goclaw_cron_run to trigger actions in GoClaw MCP Server. 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 triggers external operations (cron job execution) whose effects depend on the arguments passed (which cron job is selected). The actual outcome is determined by what the scheduled job does, making this an Execute category tool. Severity is high because unauthorized or malicious cron execution could compromise infrastructure, disrupt services, or trigger unintended automated processes.
From the tool's definition Tool name 'goclaw_cron_run' with description 'Trigger a cron job to run immediately' indicates execution of a scheduled job on-demand.
Documented attack patterns abuse exactly the kind of access goclaw_cron_run gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and GoClaw MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for goclaw_cron_run:
{
"version": "1",
"default": "deny",
"tools": {
"goclaw_cron_run": {
"limits": [
{
"counter": "goclaw_cron_run_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}goclaw_cron_run 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.
Trigger a cron job to run immediately. It is categorised as a Execute tool in the GoClaw MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the GoClaw MCP Server MCP server in PolicyLayer and add a rule for goclaw_cron_run: 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 GoClaw MCP Server. Nothing to install.
goclaw_cron_run 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 goclaw_cron_run 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 goclaw_cron_run. 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.
goclaw_cron_run is provided by the GoClaw MCP Server MCP server (nextlevelbuilder/goclaw-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from GoClaw MCP Server, 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.
66 GoClaw MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.