rc_init_fishbone · Rootcause MCP: Risk & Policy

WHAT IT DOES

What rc_init_fishbone does on Rootcause

AI agents use rc_init_fishbone 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_init_fishbone needs a policy

This tool creates a new Fishbone diagram structure for a session, which is a Write operation (creating/initializing a data structure). It is reversible (sessions can be archived/deleted) and has no destructive, financial, or execution implications. Blast radius is low as it only sets up an analytical framework within the application.

From the tool's definition Initialize a Fishbone (Ishikawa) diagram for a session

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

rc_init_fishbone Rate-limited

rc_init_fishbone 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_init_fishbone": {
      "limits": [
        {
          "counter": "rc_init_fishbone_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_init_fishbone

What does the rc_init_fishbone tool do? +

Initialize a Fishbone (Ishikawa) diagram for a 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_init_fishbone? +

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

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

Can I rate-limit rc_init_fishbone? +

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

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

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

// THE FULL RECORD

rc_init_fishbone is one line of Rootcause's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →