process_issue · Chiro ERP - Issue Pipeline Orchestrator MCP

WHAT IT DOES

What process_issue does on Chiro ERP - Issue Pipeline Orchestrator

AI agents invoke process_issue to trigger actions in Chiro ERP - Issue Pipeline Orchestrator. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why process_issue needs a policy

This tool orchestrates an entire AI-driven development workflow: analyzing requirements, designing solutions, writing and committing code, generating tests, performing reviews, and presumably opening a Pull Request. It executes external operations (GitHub API calls, code generation, PR submission) whose effects depend on the issue content.

From the tool's definition 'Automatically process a GitHub issue through the full development pipeline with role-based AI agents' — triggers multi-stage automated pipeline including code implementation, test generation, and PR creation

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

process_issue Rate-limited

process_issue stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "process_issue": {
      "limits": [
        {
          "counter": "process_issue_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Chiro ERP - Issue Pipeline Orchestrator, so you can run agents against it safely.

FAQ

Questions about process_issue

What does the process_issue tool do? +

Automatically process a GitHub issue through the full development pipeline with role-based AI agents. It is categorised as a Execute tool in the Chiro ERP - Issue Pipeline Orchestrator MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on process_issue? +

Register the Chiro ERP - Issue Pipeline Orchestrator MCP server in PolicyLayer and add a rule for process_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 Chiro ERP - Issue Pipeline Orchestrator. Nothing to install.

What risk level is process_issue? +

process_issue is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit process_issue? +

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

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

process_issue is provided by the Chiro ERP - Issue Pipeline Orchestrator MCP server (olwalgeorge2/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.