session_reboot · Iris MCP: Risk & Policy

WHAT IT DOES

What session_reboot does on Iris MCP

AI agents invoke session_reboot to trigger actions in Iris MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why session_reboot needs a policy

This tool triggers execution of a session restart operation whose effects depend on which session is targeted. While not destructive in the sense of permanent data deletion, rebooting a session can terminate ongoing work, clear temporary state, and disrupt cross-project coordination in progress. The severity is high because misuse could interrupt critical collaborative workflows across multiple codebases.

From the tool's definition Tool name 'session_reboot' and description 'Reboot a session to start fresh with a clean slate' indicates triggering an external operation that reinitializes session state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

session_reboot Rate-limited

session_reboot stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "session_reboot": {
      "limits": [
        {
          "counter": "session_reboot_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about session_reboot

What does the session_reboot tool do? +

Reboot a session to start fresh with a clean slate. It is categorised as a Execute tool in the Iris MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on session_reboot? +

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

What risk level is session_reboot? +

session_reboot is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit session_reboot? +

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

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

session_reboot is provided by the Iris MCP server (jenova-marie/iris-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.