Find users from of Rework, returns an array of users contains username, id, name, score (0-100, higher is better). Every question about user (assignee, creator, etc.) should use this tool first to get username and user id and put it into the params if needed If you want an user, and not found any...
AI agents call find_users to retrieve information from Rework MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves user information from the Rework system without creating, modifying, deleting, or executing any actions. It is a simple lookup/search function that enables other tools to obtain necessary user identifiers and metadata. The operation has no side effects and presents minimal security risk if misused by an agent—it only exposes existing user directory information.
From the tool's definition Tool description explicitly states it 'returns an array of users' with user metadata (username, id, name, score). The phrase 'find users' and 'returns' indicates a query/retrieval operation with no modification, deletion, or execution capability.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Find users from of Rework, returns an array of users contains username, id, name, score (0-100, higher is better). Every question about user (assignee, creator, etc.) should use this tool first to get username and user id and put it into the params if needed If you want an user, and not found any one yet, take the closest match. It is categorised as a Read tool in the Rework MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Rework MCP Server MCP server in PolicyLayer and add a rule for find_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 Rework MCP Server. Nothing to install.
find_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 find_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 find_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.
find_users is provided by the Rework MCP Server MCP server (rework-com/rework-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 →