list_users
Use this to enumerate users in the org when matching a person by email or building a team-wide report. Returns id, email, role, is_admin, is_active for every user.
This record as markdown: /tools/8vdx1-fundos-mcp/list-users.md
What list_users does on Fundos
AI agents call list_users to retrieve information from Fundos without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_users is rated Low
This tool queries and returns user metadata without side effects. It is a read-only enumeration tool used for matching persons and generating reports. While listing active users and admin status could inform social engineering or privilege escalation reconnaissance in a multi-step attack, the tool itself performs no destructive, financial, or state-changing actions.
From the tool's definition Tool description states it 'enumerate[s] users in the org' and 'Returns id, email, role, is_admin, is_active for every user' — purely a retrieval operation with no modification, deletion, or execution.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs list_users safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Fundos, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_users, this is the rule to start with:
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 Fundos, apply this rule, and every list_users call is checked against it from then on.
Questions about list_users
Use this to enumerate users in the org when matching a person by email or building a team-wide report. Returns id, email, role, is_admin, is_active for every user. It is categorised as a Read tool in the Fundos MCP Server, which means it retrieves data without modifying state.
Register the Fundos 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 Fundos. 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 Fundos MCP server (8vdx1/fundos-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Fundos, and thousands of servers like it.
This server
Across the catalogue