diagnose_schedule | PolicyLayer

WHAT IT DOES

What diagnose_schedule does on SchedulerRX · Constraint Debugger Agent

AI agents use diagnose_schedule to create or update resources in SchedulerRX · Constraint Debugger Agent — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SchedulerRX · Constraint Debugger Agent environment.

WHY IT NEEDS A POLICY

Why diagnose_schedule needs a policy

An AI agent can call diagnose_schedule faster than any human can review — one bad instruction and it creates or modifies resources in SchedulerRX · Constraint Debugger Agent by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

diagnose_schedule Rate-limited

diagnose_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": {
    "diagnose_schedule": {
      "limits": [
        {
          "counter": "diagnose_schedule_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 SchedulerRX · Constraint Debugger Agent, so you can run agents against it safely.

FAQ

Questions about diagnose_schedule

What does the diagnose_schedule tool do? +

diagnose_schedule. It is categorised as a Write tool in the SchedulerRX · Constraint Debugger Agent MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on diagnose_schedule? +

Register the SchedulerRX · Constraint Debugger Agent MCP server in PolicyLayer and add a rule for diagnose_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 SchedulerRX · Constraint Debugger Agent. Nothing to install.

What risk level is diagnose_schedule? +

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

Can I rate-limit diagnose_schedule? +

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

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

diagnose_schedule is provided by the SchedulerRX · Constraint Debugger Agent MCP server (tpinzzz/schedulerrx-constraint-agent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.