New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

create_issue

Open a new issue in a repository.

SERVERGitHub SOURCE@abhishekmcp/github
Medium RISK CLASS
Category Write
Parameters 43 required
Recommended Rate-limitedsee the rule below
Registry record Grade D, identity unverified Pull the record →

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.

ParameterTypeRequiredDescription
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)

Questions about create_issue

What does the create_issue tool do? +

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.

What parameters does create_issue accept? +

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.

How do I enforce a policy on create_issue? +

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.

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 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of GitHub's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.