jp_list_posts
List posts from JSONPlaceholder (fake REST API). Optionally filter by userId.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/jp-list-posts.md
What jp_list_posts does on UnClick
AI agents call jp_list_posts 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 |
|---|---|---|---|
userId | number | — | Filter by user ID (1-10) |
Parameters from the server's own tool schema.
Why jp_list_posts is rated Low
This is a straightforward data retrieval operation (list/query pattern). JSONPlaceholder is a publicly available fake REST API used for testing/demo purposes. There is no risk of modifying, deleting, or executing code. The tool simply fetches and returns posts, optionally filtered by userId. Severity is low because it operates on dummy/test data with no real-world impact.
From the tool's definition Tool description states 'List posts' with optional filtering - retrieves data from a fake REST API without modifying or deleting anything.
Attacks that exploit this kind of access
The rule that runs jp_list_posts 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_posts, this is the rule to start with:
jp_list_posts 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_posts call is checked against it from then on.
Questions about jp_list_posts
List posts from JSONPlaceholder (fake REST API). Optionally filter by userId. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
jp_list_posts accepts 1 parameter: userId. 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_posts: 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_posts 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_posts 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_posts. 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_posts 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