This record as markdown: /tools/io-github-alifanov-scopegate/github-create-issue.md
What github_create_issue does on ScopeGate
AI agents use github_create_issue to create or update resources in ScopeGate, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ScopeGate environment.
Why github_create_issue is rated Medium
Creating a GitHub issue modifies data by adding a new record but the action is reversible (the issue can be deleted). This is a Write operation. Severity is medium because misuse could spam a repository with unwanted issues, but the impact is not destructive and can be undone.
From the tool's definition Tool name is 'github_create_issue' and description states 'Create a new issue' — this creates new data (a GitHub issue) in a reversible manner.
Attacks that exploit this kind of access
The rule that runs github_create_issue safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ScopeGate, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For github_create_issue, this is the rule to start with:
github_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 ScopeGate, apply this rule, and every github_create_issue call is checked against it from then on.
Questions about github_create_issue
Create a new issue. It is categorised as a Write tool in the ScopeGate MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ScopeGate MCP server in PolicyLayer and add a rule for github_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 ScopeGate. Nothing to install.
github_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 github_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 github_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.
github_create_issue is provided by the ScopeGate MCP server (https://mcp.scopegate.cloud/{api_key}). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ScopeGate, and thousands of servers like it.
This server
Across the catalogue