schedule_create · Semaphore MCP: Risk & Policy

WHAT IT DOES

What schedule_create does on Semaphore

AI agents use schedule_create to create or update resources in Semaphore — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Semaphore environment.

WHY IT NEEDS A POLICY

Why schedule_create needs a policy

Creating a schedule in an automation workflow management system (Semaphore) is a reversible write operation—the schedule can be modified or deleted later. This is less severe than Destructive (irreversible) or Execute (arbitrary code), but more impactful than Read.

From the tool's definition Tool name 'schedule_create' indicates creation of a new schedule object. Sibling tools show a pattern: environment_create, inventory_create are Write operations; environment_delete, inventory_delete, key_delete are Destructive.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

schedule_create Rate-limited

schedule_create 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": {
    "schedule_create": {
      "limits": [
        {
          "counter": "schedule_create_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Semaphore, so you can run agents against it safely.

FAQ

Questions about schedule_create

What does the schedule_create tool do? +

schedule_create. It is categorised as a Write tool in the Semaphore MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on schedule_create? +

Register the Semaphore MCP server in PolicyLayer and add a rule for schedule_create: 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 Semaphore. Nothing to install.

What risk level is schedule_create? +

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

Can I rate-limit schedule_create? +

Yes. Add a rate_limit block to the schedule_create 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 schedule_create completely? +

Set action: deny in the PolicyLayer policy for schedule_create. 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 schedule_create? +

schedule_create is provided by the Semaphore MCP server (vitexsoftware/semaphore-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.