Create a GitHub issue (can trigger Claude Code)
AI agents use create_github_issue to create or update resources in Obsidian Ai Curator — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Obsidian Ai Curator environment.
This tool creates a new GitHub issue, which is a reversible write operation on external infrastructure. While it mentions the ability to trigger Claude Code (which could elevate to Execute), the core function is writing data. The severity is medium because creating issues on a public repository could have moderate consequences (spam, invalid issues), but it's not inherently destructive or financial.
From the tool's definition Tool name 'create_github_issue' and description 'Create a GitHub issue' indicates data creation. The parenthetical '(can trigger Claude Code)' suggests potential for triggering external operations, but the primary function is creating/writing an issue record.
Documented attack patterns abuse exactly the kind of access create_github_issue gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Obsidian Ai Curator, and nothing reaches the server without passing your rules. This is the rule we recommend for create_github_issue:
{
"version": "1",
"default": "deny",
"tools": {
"create_github_issue": {
"limits": [
{
"counter": "create_github_issue_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_github_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 GitHub issue (can trigger Claude Code). It is categorised as a Write tool in the Obsidian Ai Curator MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Obsidian Ai Curator MCP server in PolicyLayer and add a rule for create_github_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 Obsidian Ai Curator. Nothing to install.
create_github_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_github_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_github_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_github_issue is provided by the Obsidian Ai Curator MCP server (nwant/obsidian-ai-curator). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Obsidian Ai Curator, 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.
27 Obsidian Ai Curator tools catalogued and risk-classified — across an index of 43,000+ MCP servers.