github_create_issue · Integrations MCP: Risk & Policy

WHAT IT DOES

What github_create_issue does on Integrations MCP

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

WHY IT NEEDS A POLICY

Why github_create_issue needs a policy

Creating a GitHub issue modifies data (adds a new issue to a repository) but the action is reversible (the issue can be deleted). This is a Write operation. Severity is medium because misuse could spam repositories with unwanted issues, affecting team workflows, but causes no permanent damage or financial impact.

From the tool's definition Tool name 'github_create_issue' indicates creation of a new GitHub issue, which is a reversible write operation. Description is empty, reducing confidence slightly.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

github_create_issue Rate-limited

github_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": {
    "github_create_issue": {
      "limits": [
        {
          "counter": "github_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 Integrations MCP, so you can run agents against it safely.

FAQ

Questions about github_create_issue

What does the github_create_issue tool do? +

github_create_issue. It is categorised as a Write tool in the Integrations MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on github_create_issue? +

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

What risk level is github_create_issue? +

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

Can I rate-limit github_create_issue? +

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

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

github_create_issue is provided by the Integrations MCP server (shriram-vasudevan/integrations-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.