rc_export_why_tree · Rootcause MCP: Risk & Policy

WHAT IT DOES

What rc_export_why_tree does on Rootcause

AI agents use rc_export_why_tree 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_export_why_tree needs a policy

This tool exports analytical data (a Why Tree artifact) into various formats, which constitutes creating or modifying output rather than destructively altering source data. The action is reversible—exported data can be regenerated. No financial transactions, code execution, or permanent deletion occurs.

From the tool's definition Tool name 'rc_export_why_tree' and description 'Export Why Tree in various formats' indicate data exfiltration/extraction capabilities. 'Export' typically involves writing data to a new format or destination without reversing existing data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

rc_export_why_tree Rate-limited

rc_export_why_tree 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_export_why_tree": {
      "limits": [
        {
          "counter": "rc_export_why_tree_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_export_why_tree

What does the rc_export_why_tree tool do? +

Export Why Tree in various formats. 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_export_why_tree? +

Register the Rootcause MCP server in PolicyLayer and add a rule for rc_export_why_tree: 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_export_why_tree? +

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

Can I rate-limit rc_export_why_tree? +

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

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

rc_export_why_tree 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.