jp_list_comments
List comments on a post from JSONPlaceholder.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/jp-list-comments.md
What jp_list_comments does on UnClick
AI agents call jp_list_comments to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
postId | number | Yes | Post ID to get comments for |
Parameters from the server's own tool schema.
Why jp_list_comments is rated Low
This tool queries and retrieves comments from a JSONPlaceholder post, which is a publicly available mock data API. The operation is read-only, returns existing data without creating, modifying, or deleting anything, and has minimal blast radius even if misused by an AI agent (worst case: retrieving public test data).
From the tool's definition Tool name includes 'list' and description states 'List comments on a post' — a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs jp_list_comments safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For jp_list_comments, this is the rule to start with:
jp_list_comments is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every jp_list_comments call is checked against it from then on.
Questions about jp_list_comments
List comments on a post from JSONPlaceholder. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
jp_list_comments accepts 1 parameter: postId. Required: postId. 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 jp_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.
jp_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 jp_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 jp_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.
jp_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.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue