This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/reqres-get-user.md
What reqres_get_user does on UnClick
AI agents call reqres_get_user 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 |
|---|---|---|---|
id | number | Yes | User ID (1-12) |
Parameters from the server's own tool schema.
Why reqres_get_user is rated Low
This tool retrieves data from a fake/test API (Reqres is a well-known mock API service) without modifying, deleting, or executing external operations. The data is explicitly fake, further reducing any potential impact. This is a straightforward Read operation with minimal risk.
From the tool's definition Tool name and description indicate retrieval only: 'Get a specific fake user by ID from Reqres.' The verb 'Get' and the qualifier 'fake user' confirm this is a read-only query operation with no side effects.
Attacks that exploit this kind of access
The rule that runs reqres_get_user 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 reqres_get_user, this is the rule to start with:
reqres_get_user 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 reqres_get_user call is checked against it from then on.
Questions about reqres_get_user
Get a specific fake user by ID from Reqres. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
reqres_get_user accepts 1 parameter: id. Required: id. 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 reqres_get_user: 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.
reqres_get_user 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 reqres_get_user 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 reqres_get_user. 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.
reqres_get_user 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