disable_schedule

Disable an active schedule.

SERVERAutomagik Tools SOURCEnamastexlabs/automagik-tools

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/namastexlabs-automagik-tools/disable-schedule.md

WHAT IT DOES

What disable_schedule does on Automagik Tools

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.

RISK

Why disable_schedule is rated Medium

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.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs disable_schedule safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Automagik Tools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For disable_schedule, this is the rule to start with:

disable_schedule Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "disable_schedule": {
      "limits": [
        {
          "counter": "disable_schedule_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Automagik Tools, apply this rule, and every disable_schedule call is checked against it from then on.

FAQ

Questions about disable_schedule

What does the disable_schedule tool do? +

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.

How do I enforce a policy on disable_schedule? +

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.

What risk level is disable_schedule? +

disable_schedule is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit disable_schedule? +

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.

How do I block disable_schedule completely? +

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.

What MCP server provides disable_schedule? +

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.

KEEP EXPLORING

More on Automagik Tools, and thousands of servers like it.

This server

All 122 Automagik Tools tools →

Across the catalogue

sms_schedule on Twilio SMS MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →