AI agents use create_issue to create or update resources in Gitee — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gitee environment.
The tool creates new data (an issue) in a repository, which is a reversible write operation. It does not execute code, delete data, or move money. The severity is medium because malicious issue creation could spam/disrupt a repository and its workflows, but the impact is contained and reversible. Confidence is high given the clear function name and purpose.
From the tool's definition Tool name is 'create_issue' and description states '在 Gitee 仓库中创建 Issue' (creates an Issue in a Gitee repository). This is a creation operation that modifies repository state by adding a new issue.
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 Gitee, 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.
在 Gitee 仓库中创建 Issue. It is categorised as a Write tool in the Gitee MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Gitee 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 Gitee. 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 Gitee MCP server (normal-coder/gitee-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Gitee, 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.
20 Gitee tools catalogued and risk-classified — across an index of 43,000+ MCP servers.