create_issue · GitHub Repos Manager MCP Server MCP

WHAT IT DOES

What create_issue does on GitHub Repos Manager MCP Server

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

THE RISK

Medium Risk

Why create_issue needs a policy

Creating an issue is a write operation that adds data to a repository reversibly. While it modifies repository state, issues can be closed or deleted, making it Write rather than Destructive. The severity is medium because an AI agent could spam issues, create misleading bug reports, or clutter a repository, but the impact is limited to that single repository and can be undone.

From the tool's definition Tool name is 'create_issue' and description states 'Create a new issue in a repository' — this creates new data in a GitHub repository.

Documented attack patterns abuse exactly the kind of access create_issue gives an agent:

POLICY

How to control create_issue

PolicyLayer is an MCP gateway — it sits between your AI agents and GitHub Repos Manager MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create_issue:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_issue": {
      "limits": [
        {
          "counter": "create_issue_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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.

Create a free account and register GitHub Repos Manager MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More GitHub Repos Manager MCP Server tools

Destructive delete_deploy_key Remove deploy keys. Destructive delete_file Delete a file from a repository. Destructive delete_issue_comment Delete an issue comment Destructive delete_label Delete a label from a repository Destructive delete_milestone Delete a milestone Destructive delete_webhook Remove webhooks. Execute cancel_workflow_run Cancel running workflows. Execute trigger_workflow Manually trigger workflow dispatches (handle input parameters).

All 84 GitHub Repos Manager MCP Server tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about create_issue

What does the create_issue tool do? +

Create a new issue in a repository. It is categorised as a Write tool in the GitHub Repos Manager MCP Server 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 GitHub Repos Manager MCP Server 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 GitHub Repos Manager MCP Server. 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 GitHub Repos Manager MCP Server MCP server (kurdin/github-repos-manager-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every GitHub Repos Manager MCP Server tool call.

Start from GitHub Repos Manager MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

84 GitHub Repos Manager MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.