AI agents call list_comments to retrieve information from UnClick without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | number | — | |
agent_id | string | Yes | |
target_id | string | Yes | |
target_kind | string | Yes |
Parameters from the server's own tool schema.
This tool retrieves and queries existing comment data in chronological order. It has no capability to modify, delete, or execute operations. The only parameter mentioned (agent_id) is a required identifier for the query. This is a straightforward read operation with minimal blast radius—misuse would only expose comment data already accessible to the agent.
From the tool's definition Tool description states it 'Returns comments' on a Boardroom todo or idea. The verb 'Returns' indicates data retrieval with no modification or side effects. No parameters suggest deletion, creation, or execution of operations.
Attacks that exploit this kind of access
Returns comments on a specific Boardroom todo or idea, in chronological order. agent_id required. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
list_comments accepts 4 parameters: limit, agent_id, target_id, target_kind. Required: 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 list_comments: 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.
list_comments is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_comments 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 list_comments. 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.
list_comments 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 →