AI agents use comment_on to create or update resources in UnClick — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your UnClick environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
text | string | Yes | Comment body (max 4000 chars) |
agent_id | string | Yes | |
target_id | string | Yes | |
target_kind | string | Yes |
Parameters from the server's own tool schema.
This tool creates new comment data (reversible write operation) on collaborative platform items. It does not execute code, delete data, or move money. Severity is medium because an AI agent could spam comments, post inappropriate content, or disrupt team discussions by adding numerous unwanted comments, but the operation is reversible and limited to comment creation rather than destructive modification of the…
From the tool's definition Tool name 'comment_on' with description stating it 'Adds a comment' to Boardroom items. 'Adds' is explicit write/create terminology. Creates new comment data within a scoped discussion context.
Attacks that exploit this kind of access
Adds a comment to a Boardroom todo or idea. Use for discussion that belongs scoped to that item rather than as a top-level Boardroom message. target_kind is 'todo' or 'idea'. agent_id required. It is categorised as a Write tool in the UnClick MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
comment_on accepts 4 parameters: text, agent_id, target_id, target_kind. Required: text, agent_id, target_id, target_kind. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for comment_on: 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 UnClick. Nothing to install.
comment_on 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 comment_on 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 comment_on. 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.
comment_on is provided by the UnClick MCP server (@unclick/mcp-server). 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 →