ralph_hero__batch_update · Ralph Hero MCP: Risk & Policy

WHAT IT DOES

What ralph_hero__batch_update does on Ralph Hero

AI agents use ralph_hero__batch_update 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__batch_update needs a policy

This tool creates or modifies project data (workflow state, estimates, priority) across multiple issues reversibly. While updates are not destructive (can be reversed), the bulk nature and potential to affect many issues simultaneously elevates severity to high. It is Write rather than Execute because it modifies structured data fields rather than executing arbitrary code.

From the tool's definition 'Bulk-update project fields (workflow state, estimate, priority) across multiple issues in a single call' — modifies project metadata across multiple items; 'Returns: succeeded, skipped, errors arrays' confirms write operations occur.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ralph_hero__batch_update Rate-limited

ralph_hero__batch_update 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__batch_update": {
      "limits": [
        {
          "counter": "ralph_hero__batch_update_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__batch_update

What does the ralph_hero__batch_update tool do? +

Bulk-update project fields (workflow state, estimate, priority) across multiple issues in a single call. Uses aliased GraphQL for efficiency (~2 API calls instead of 3N). Returns: succeeded, skipped, errors arrays with per-issue status. Recovery: partial failures don. 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__batch_update? +

Register the Ralph Hero MCP server in PolicyLayer and add a rule for ralph_hero__batch_update: 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__batch_update? +

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

Can I rate-limit ralph_hero__batch_update? +

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

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

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