Create a new issue in a GitHub repository
AI agents use create_issue to create or update resources in Claude TypeScript MCP Servers — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Claude TypeScript MCP Servers environment.
This tool creates new issues reversibly within GitHub. It modifies state by adding a record but does not delete, execute code, move money, or perform irreversible actions. The severity is medium because misuse could spam repositories or create misleading issues, affecting collaboration workflows and repository integrity, but damage can be remediated by deleting issues.
From the tool's definition Tool name 'create_issue' and description 'Create a new issue in a GitHub repository' indicate creation of new data in an external system (GitHub).
Documented attack patterns abuse exactly the kind of access create_issue gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Claude TypeScript MCP Servers, and nothing reaches the server without passing your rules. This is the rule we recommend for create_issue:
{
"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.
Free to start. No card required.
Create a new issue in a GitHub repository. It is categorised as a Write tool in the Claude TypeScript MCP Servers MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Claude TypeScript MCP Servers 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 Claude TypeScript MCP Servers. 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 Claude TypeScript MCP Servers MCP server (ukkz/claude-ts-mcps). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Claude TypeScript MCP Servers, 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.
84 Claude TypeScript MCP Servers tools catalogued and risk-classified — across an index of 43,000+ MCP servers.