AI agents call list_users to retrieve information from Pearlog without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
activeOnly | boolean | — | If true, return only active users. Defaults to false. |
Parameters from the server's own tool schema.
This tool retrieves user information from the Pearlog system without modifying, deleting, or executing any operations. It is a straightforward list/query operation that returns data for informational purposes. The blast radius of misuse is minimal—an agent could see all users but cannot act on this information destructively without separate tools like delete_ticket or move_ticket.
From the tool's definition Tool name 'list_users' and description 'List all users in the Pearlog instance' indicate a retrieval operation with no side effects. The stated purpose is to 'find user IDs for ticket assignment,' which is a read-only query.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
List all users in the Pearlog instance. Use this to find user IDs for ticket assignment. It is categorised as a Read tool in the Pearlog MCP Server, which means it retrieves data without modifying state.
list_users accepts 1 parameter: activeOnly. The full parameter table on this page comes from the server's own tool schema.
Register the Pearlog MCP server in PolicyLayer and add a rule for 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 Pearlog. Nothing to install.
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 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 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.
list_users is provided by the Pearlog MCP server (mcp-server-pearlog). 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 →