This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/reqres-list-users.md
What reqres_list_users does on UnClick
AI agents call reqres_list_users 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 |
|---|---|---|---|
page | number | — | Page number (default 1) |
Parameters from the server's own tool schema.
Why reqres_list_users is rated Low
This tool retrieves or queries data from a test API with no side effects. It is a Read operation. The severity is low because it accesses only fake test data from a public service, presenting minimal risk even if misused by an AI agent.
From the tool's definition Tool name contains 'list' and description states 'List fake users from Reqres (test API)'. The Reqres service is a well-known public testing API that provides mock data. No modifications, deletions, or external operations are indicated.
Attacks that exploit this kind of access
The rule that runs reqres_list_users 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_list_users, this is the rule to start with:
reqres_list_users 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_list_users call is checked against it from then on.
Questions about reqres_list_users
List fake users from Reqres (test API). It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
reqres_list_users accepts 1 parameter: page. 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_list_users: 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_list_users 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_list_users 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_list_users. 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_list_users 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