create_issue · Multi-MCPs MCP: Risk & Policy

WHAT IT DOES

What create_issue does on Multi-MCPs

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

WHY IT NEEDS A POLICY

Why create_issue needs a policy

This tool creates new data (a GitHub issue) in a repository. Creating issues is a reversible action — they can be closed, deleted, or modified afterward. It does not execute arbitrary code, delete data permanently, or move money.

From the tool's definition Tool name is 'create_issue' and description states 'Create an issue in a repository' — this creates new content (an issue/ticket) in a repository, which is a reversible write operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_issue Rate-limited

create_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": {
    "create_issue": {
      "limits": [
        {
          "counter": "create_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 Multi-MCPs, so you can run agents against it safely.

FAQ

Questions about create_issue

What does the create_issue tool do? +

Create an issue in a repository. It is categorised as a Write tool in the Multi-MCPs MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_issue? +

Register the Multi-MCPs MCP server in PolicyLayer and add a rule for create_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 Multi-MCPs. Nothing to install.

What risk level is create_issue? +

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

Can I rate-limit create_issue? +

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

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

create_issue is provided by the Multi-MCPs MCP server (taylorchen/muti-mcps). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.