This record as markdown: /tools/io-github-portel-dev-ncp/create-issue.md
What create_issue does on Ncp
AI agents use create_issue to create or update resources in Ncp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ncp environment.
Why create_issue is rated Medium
This tool creates a new issue, which is a write operation that modifies state in GitHub. It is reversible (issues can be deleted or closed), so it does not qualify as Destructive. There is no financial impact, code execution, or data retrieval involved. The severity is medium because creating issues could be abused to spam a repository, but the impact is limited and contained to one repository's issue tracker.
From the tool's definition Tool description states 'Create a new issue in a GitHub repository' — this creates new data in an external system (GitHub) in a reversible manner.
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 Ncp, 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 Ncp, apply this rule, and every create_issue call is checked against it from then on.
Questions about create_issue
Create a new issue in a GitHub repository. It is categorised as a Write tool in the Ncp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ncp 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 Ncp. 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 Ncp MCP server (@portel/ncp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ncp, and thousands of servers like it.
This server
Across the catalogue