This record as markdown: /tools/io-github-kivanccakmak-yaver/github-issue-create.md
What github_issue_create does on Yaver
AI agents use github_issue_create to create or update resources in Yaver, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Yaver environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
body | string | — | |
title | string | Yes | |
labels | array | — | |
directory | string | — |
Parameters from the server's own tool schema.
Why github_issue_create is rated Medium
This tool creates (writes) a new GitHub issue, which is a reversible action. The issue can be edited or closed if needed. Severity is medium because misuse could spam a repository with unwanted issues, disrupt workflows, and potentially violate repository policies, but the action is not destructive (issues aren't permanently lost) and doesn't involve financial transactions or code execution on the user's system.
From the tool's definition Tool name 'github_issue_create' and description 'Open a GitHub issue' indicates creation of a new issue resource on GitHub.
Risk signalsAccepts file system path (directory) · Accepts raw HTML/template content (body)
Attacks that exploit this kind of access
The rule that runs github_issue_create safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For github_issue_create, this is the rule to start with:
github_issue_create 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 Yaver, apply this rule, and every github_issue_create call is checked against it from then on.
Questions about github_issue_create
Open a GitHub issue. It is categorised as a Write tool in the Yaver MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
github_issue_create accepts 4 parameters: body, title, labels, directory. Required: title. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver MCP server in PolicyLayer and add a rule for github_issue_create: 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 Yaver. Nothing to install.
github_issue_create 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_issue_create 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_issue_create. 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_issue_create is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Yaver, and thousands of servers like it.
This server
Across the catalogue