Medium Risk

create_issue

Create a new issue in a AtomGit repository

How to control create_issue ↓

What create_issue does on AtomGit MCP Server

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

Medium Risk

Why create_issue needs a policy

Creating an issue is a write operation that modifies repository state by adding new data. It is reversible (the issue can be deleted or closed) and does not execute code, delete data irreversibly, or involve financial transactions.

From the tool's definition Tool description explicitly states 'Create a new issue', which is a reversible data modification operation. The tool creates new content in the repository without deleting or executing arbitrary code.

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

How to control create_issue

PolicyLayer is an MCP gateway — it sits between your AI agents and AtomGit 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.

  1. Create a free account and register AtomGit MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about create_issue

What does the create_issue tool do? +

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

Enforce policy on every AtomGit MCP Server tool call.

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

Free to start. No card required.

22 AtomGit MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.