This record as markdown: /tools/com-files-python-mcp/list-user.md
What List_User does on Files Com
AI agents call List_User to retrieve information from Files Com without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why List_User is rated Low
This tool retrieves user information from the Files.com environment. The verb 'List' is a classic read operation (analogous to 'get' or 'fetch') that queries data without creating, modifying, or deleting anything. The sibling tools include destructive actions (Delete_Bundle) and write operations (Create_User, Create_Folder), but this tool is explicitly a listing operation, making it a Read category with low severity.
From the tool's definition Tool name 'List_User' and description 'List Users' indicate a query/retrieval operation with no side effects. Listing is a read-only operation that retrieves existing data without modification, deletion, or execution.
Attacks that exploit this kind of access
The rule that runs List_User safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Files Com, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For List_User, this is the rule to start with:
List_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 Files Com, apply this rule, and every List_User call is checked against it from then on.
Questions about List_User
List Users. It is categorised as a Read tool in the Files Com MCP Server, which means it retrieves data without modifying state.
Register the Files Com MCP server in PolicyLayer and add a rule for List_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 Files Com. Nothing to install.
List_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 List_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 List_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.
List_User is provided by the Files Com MCP server (files-com-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Files Com, and thousands of servers like it.
This server
Across the catalogue