ralph_hero__add_sub_issue · Ralph Hero MCP: Risk & Policy

WHAT IT DOES

What ralph_hero__add_sub_issue does on Ralph Hero

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

WHY IT NEEDS A POLICY

Why ralph_hero__add_sub_issue needs a policy

This tool creates a new relationship structure between existing issues, which is a reversible modification (the relationship can be removed). It does not execute arbitrary code, delete data irreversibly, or move money. The severity is medium because misuse could create confusing issue hierarchies or organizational chaos in a project, but the impact is contained to issue relationship metadata and easily reversible.

From the tool's definition The tool description states it creates a "parent/child (sub-issue) relationship between two GitHub issues," which is a create operation that modifies the structure and metadata of issues without deleting or overwriting data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ralph_hero__add_sub_issue Rate-limited

ralph_hero__add_sub_issue 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": {
    "ralph_hero__add_sub_issue": {
      "limits": [
        {
          "counter": "ralph_hero__add_sub_issue_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 Ralph Hero, so you can run agents against it safely.

FAQ

Questions about ralph_hero__add_sub_issue

What does the ralph_hero__add_sub_issue tool do? +

Create a parent/child (sub-issue) relationship between two GitHub issues. The parent issue becomes the container for the child issue. It is categorised as a Write tool in the Ralph Hero MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on ralph_hero__add_sub_issue? +

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

What risk level is ralph_hero__add_sub_issue? +

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

Can I rate-limit ralph_hero__add_sub_issue? +

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

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

ralph_hero__add_sub_issue is provided by the Ralph Hero MCP server (ralph-hero-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.