AI agents use update_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.
This tool creates or modifies issue data in a reversible manner. Updates to issues can typically be undone through subsequent edits or version history. It does not delete data (which would be Destructive), does not execute arbitrary code (which would be Execute), and does not involve financial transactions.
From the tool's definition Tool name 'update_issue' and description '更新 Gitee 仓库中的 Issue' (Update Issue in Gitee repository) indicates modification of existing issue data. The verb '更新' (update) is a write operation that modifies data reversibly.
Documented attack patterns abuse exactly the kind of access update_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 update_issue:
{
"version": "1",
"default": "deny",
"tools": {
"update_issue": {
"limits": [
{
"counter": "update_issue_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_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 update_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.
update_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 update_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 update_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.
update_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.