This record as markdown: /tools/io-github-abhishekkumar2021-github/create-issue.md
What create_issue does on GitHub
AI agents use create_issue to create or update resources in GitHub, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GitHub environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
body | string | — | |
repo | string | Yes | Repository name |
owner | string | Yes | Repository owner (user or org) |
title | string | Yes |
Parameters from the server's own tool schema.
Why create_issue is rated Medium
This tool creates new content (an issue) in a repository, making it a Write operation. It is not Read (does not merely query), not Execute (does not run code or trigger arbitrary operations), not Destructive (the issue can be closed or deleted), and not Financial.
From the tool's definition Tool description states 'Open a new issue in a repository' — this creates new data (an issue) that persists in the repository. The tool modifies repository state by adding a new issue, which is reversible (issues can be closed or deleted).
Risk signalsAccepts raw HTML/template content (body)
Attacks that exploit this kind of access
The rule that runs create_issue safely
PolicyLayer is an MCP gateway: it sits between your AI agents and GitHub, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_issue, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect GitHub, apply this rule, and every create_issue call is checked against it from then on.
Questions about create_issue
Open a new issue in a repository. It is categorised as a Write tool in the GitHub MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_issue accepts 4 parameters: body, repo, owner, title. Required: repo, owner, title. The full parameter table on this page comes from the server's own tool schema.
Register the GitHub 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. Nothing to install.
create_issue is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
create_issue is provided by the GitHub MCP server (@abhishekmcp/github). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on GitHub, and thousands of servers like it.
This server
Across the catalogue