Adds, edits, or deletes a comment on an issue. Returns structured data with the comment URL, operation type, comment ID, issue number, and body echo.
AI agents use issue-comment to create or update resources in Make — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Make environment.
This tool creates or modifies comments on issues, which is a reversible write operation. Although it includes a delete capability, the emphasis on add/edit and the structured return of modified data suggest this is primarily a Write-category tool rather than Destructive, since comment deletion is typically recoverable in most issue tracking systems and the tool appears designed for comment management rather than…
From the tool's definition Tool description states it 'Adds, edits, or deletes a comment on an issue' - the add and edit operations are reversible modifications of data. While deletion is mentioned, the primary operations are write-class (add/edit).
Documented attack patterns abuse exactly the kind of access issue-comment gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Make, and nothing reaches the server without passing your rules. This is the rule we recommend for issue-comment:
{
"version": "1",
"default": "deny",
"tools": {
"issue-comment": {
"limits": [
{
"counter": "issue-comment_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
Adds, edits, or deletes a comment on an issue. Returns structured data with the comment URL, operation type, comment ID, issue number, and body echo. It is categorised as a Write tool in the Make MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Make MCP server in PolicyLayer and add a rule for 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 Make. Nothing to install.
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 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 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.
issue-comment is provided by the Make MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Make, 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.
202 Make tools catalogued and risk-classified — across an index of 43,000+ MCP servers.