rc_archive_session · Rootcause MCP: Risk & Policy

WHAT IT DOES

What rc_archive_session does on Rootcause

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

WHY IT NEEDS A POLICY

Why rc_archive_session needs a policy

Archiving a session changes its status/metadata but is reversible (can be unarchived), making it a Write rather than Destructive action. The severity is medium because archiving could impact ongoing clinical education workflows or incident documentation accessibility, but the action itself doesn't delete data or cause financial harm.

From the tool's definition Tool name 'rc_archive_session' and description 'Archive a completed RCA session' indicate a state-change operation that modifies session metadata (moving to archived status), a reversible write action.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

rc_archive_session Rate-limited

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

FAQ

Questions about rc_archive_session

What does the rc_archive_session tool do? +

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

How do I enforce a policy on rc_archive_session? +

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

What risk level is rc_archive_session? +

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

Can I rate-limit rc_archive_session? +

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

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

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