rh11_schedule_set · Rhodium11 MCP: Risk & Policy

WHAT IT DOES

What rh11_schedule_set does on Rhodium11

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

WHY IT NEEDS A POLICY

Why rh11_schedule_set needs a policy

This is a Write operation because it creates or modifies data reversibly. The tool updates a project's schedule configuration by replacing the entire schedule with new entries. While it modifies critical operational data (daily volumes for multiple parameters), the changes are reversible through subsequent calls to set a different schedule.

From the tool's definition Tool description states 'Set the full per-day schedule for a Rhodium11 project. Replaces any existing schedule.' The action modifies project schedule data and overwrites existing entries.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

rh11_schedule_set Rate-limited

rh11_schedule_set 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": {
    "rh11_schedule_set": {
      "limits": [
        {
          "counter": "rh11_schedule_set_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 Rhodium11, so you can run agents against it safely.

FAQ

Questions about rh11_schedule_set

What does the rh11_schedule_set tool do? +

Set the full per-day schedule for a Rhodium11 project. Replaces any existing schedule. Each entry represents one day with volumes for atc, sfb, pgv, and wishlist. Max 365 entries. SFB units that fall in the next 2 days (mpux-flask LOCK_SFB_DAYS, configurable via RH11_LOCK_SFB_DAYS) become committed once the project has active SFB —. It is categorised as a Write tool in the Rhodium11 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on rh11_schedule_set? +

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

What risk level is rh11_schedule_set? +

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

Can I rate-limit rh11_schedule_set? +

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

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

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