gluecron_comment_issue
Add a comment to an existing issue. Requires authenticated caller with write access. Returns {commentId}.
This record as markdown: /tools/com-gluecron-gluecron/gluecron-comment-issue.md
What gluecron_comment_issue does on Gluecron
AI agents use gluecron_comment_issue to create or update resources in Gluecron, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gluecron environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
body | string | Yes | Comment body (Markdown) |
repo | string | Yes | Repo name |
owner | string | Yes | Repo owner username |
number | number | Yes | Issue number |
Parameters from the server's own tool schema.
Why gluecron_comment_issue is rated Medium
Adding a comment creates new data in the issue tracker and modifies the issue's state irreversibly (though comments can typically be edited/deleted by admins, the primary action is constructive rather than destructive). Severity is medium because blast radius is limited to issue metadata/communication on a single repo; does not affect production code or financial systems.
From the tool's definition Tool name contains 'comment' and description states 'Add a comment to an existing issue' — a create/modify operation. Requires 'write access' confirming it modifies state.
Risk signalsAccepts raw HTML/template content (body)
Attacks that exploit this kind of access
The rule that runs gluecron_comment_issue safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gluecron, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For gluecron_comment_issue, this is the rule to start with:
gluecron_comment_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Gluecron, apply this rule, and every gluecron_comment_issue call is checked against it from then on.
Questions about gluecron_comment_issue
Add a comment to an existing issue. Requires authenticated caller with write access. Returns {commentId}. It is categorised as a Write tool in the Gluecron MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
gluecron_comment_issue accepts 4 parameters: body, repo, owner, number. Required: body, repo, owner, number. The full parameter table on this page comes from the server's own tool schema.
Register the Gluecron MCP server in PolicyLayer and add a rule for gluecron_comment_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 Gluecron. Nothing to install.
gluecron_comment_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 gluecron_comment_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 gluecron_comment_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.
gluecron_comment_issue is provided by the Gluecron MCP server (https://gluecron.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gluecron, and thousands of servers like it.
This server
Across the catalogue