AI agents use create_comment 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 | Yes | The contents of the comment |
repo | string | Yes | The path of the repository |
owner | string | Yes | The space address to which the repository belongs (enterprise, organization or personal path) |
number | string | Yes | Issue or pull request number (case sensitive, no # prefix needed) |
resource_type | string | Yes | Resource type: issue or pull |
Parameters from the server's own tool schema.
This tool creates new comments, which is a write operation that modifies the state of an issue or pull request by adding reversible content. While comments can be edited or deleted later, the primary action is content creation.
From the tool's definition Tool description states 'Create a comment on an issue or pull request' - explicitly creates new content that can be added to a repository's issue/PR tracking system.
Risk signalsAccepts raw HTML/template content (body)
Attacks that exploit this kind of access
Create a comment on an issue or pull request. 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.
create_comment accepts 5 parameters: body, repo, owner, number, resource_type. Required: body, repo, owner, number, resource_type. 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 create_comment: 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.
create_comment 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_comment 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_comment. 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_comment 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 →