AI agents use disable_schedule to create or update resources in Automagik Tools — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Automagik Tools environment.
The tool modifies scheduling configuration by disabling an active schedule, which is a Write operation—data is changed but the action is reversible (the schedule can be re-enabled). This is not destructive (data isn't deleted), not financial, and not Execute (no code/command execution indicated).
From the tool's definition Tool name 'disable_schedule' indicates modification of a schedule configuration from active to disabled state. This is a reversible state change operation.
Documented attack patterns abuse exactly the kind of access disable_schedule gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Automagik Tools, and nothing reaches the server without passing your rules. This is the rule we recommend for disable_schedule:
{
"version": "1",
"default": "deny",
"tools": {
"disable_schedule": {
"limits": [
{
"counter": "disable_schedule_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}disable_schedule stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Disable an active schedule. It is categorised as a Write tool in the Automagik Tools MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Automagik Tools MCP server in PolicyLayer and add a rule for disable_schedule: 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 Automagik Tools. Nothing to install.
disable_schedule is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the disable_schedule 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 disable_schedule. 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.
disable_schedule is provided by the Automagik Tools MCP server (namastexlabs/automagik-tools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Automagik Tools, 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.
122 Automagik Tools tools catalogued and risk-classified — across an index of 43,000+ MCP servers.