AI agents use update_issue to create or update resources in Mcp Gitee — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Gitee environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
body | string | — | The description of the issue |
repo | string | Yes | The path of the repository |
owner | string | Yes | The space address to which the repository belongs (the address path of the enterprise, organization or individual) |
state | string | — | The state of the issue |
title | string | Yes | The title of the issue |
labels | string | — | Comma-separated labels, name requirements are between 2-20 in length and non-special characters. Example: bug,performance |
number | string | Yes | The number of the issue |
program | string | — | Project ID |
assignee | string | — | The personal space address of the issue assignee |
milestone | string | — | The milestone number |
issue_type | string | — | Enterprise custom task type, non-enterprise users must consider it as 'task' |
collaborators | string | — | The personal space addresses of issue collaborators, separated by commas |
Parameters from the server's own tool schema.
This tool modifies issue records on Gitee but does not delete or irreversibly destroy data. Updates to issues are reversible through subsequent corrections or version history. The blast radius is medium—an agent could spam issue updates or corrupt issue metadata, but the damage is bounded to the issue tracking system and can be undone.
From the tool's definition Tool name is 'update_issue' with description 'Update an issue'. The verb 'update' indicates modification of existing data (issue fields, status, assignee, labels, etc.) in a reversible manner.
Risk signalsAccepts raw HTML/template content (body) · High parameter count (13 properties)
Attacks that exploit this kind of access
Update an issue. It is categorised as a Write tool in the Mcp Gitee MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
update_issue accepts 12 parameters: body, repo, owner, state, title, labels, number, program, assignee, milestone, issue_type, collaborators. Required: repo, owner, title, number. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp 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 Mcp 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 Mcp Gitee MCP server (@gitee/mcp-gitee). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →