This record as markdown: /tools/sqcows-forgejo-mcp/create-issue-comment.md
What create_issue_comment does on Forgejo
AI agents use create_issue_comment to create or update resources in Forgejo, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Forgejo environment.
Why create_issue_comment is rated Medium
Creating a comment is a Write operation: it adds data to the system but does not delete, destroy, execute code, or cause financial impact. The action is reversible (comments can be edited or deleted). Blast radius is low since comments are typically not sensitive and do not affect repository integrity or system behavior directly.
From the tool's definition Tool name is 'create_issue_comment' and description states 'Add a comment to an issue' — this creates new data (a comment) in a reversible manner.
Attacks that exploit this kind of access
The rule that runs create_issue_comment safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Forgejo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_issue_comment, this is the rule to start with:
create_issue_comment 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 Forgejo, apply this rule, and every create_issue_comment call is checked against it from then on.
Questions about create_issue_comment
Add a comment to an issue. It is categorised as a Write tool in the Forgejo MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Forgejo MCP server in PolicyLayer and add a rule for create_issue_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 Forgejo. Nothing to install.
create_issue_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_issue_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_issue_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_issue_comment is provided by the Forgejo MCP server (sqcows/forgejo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Forgejo, and thousands of servers like it.
This server
Across the catalogue