list_room_members
Use this to list members of a deal room when checking who has access before granting more or before sharing sensitive content. Returns user_id, email, role, and per-folder permissions.
This record as markdown: /tools/8vdx1-fundos-mcp/list-room-members.md
What list_room_members does on Fundos
AI agents call list_room_members 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_room_members is rated Low
This tool retrieves and queries existing data about deal room membership and access permissions without creating, modifying, deleting, or executing any operations. It is informational only, used for visibility into access control.
From the tool's definition Tool name is 'list_room_members' and description states it 'list members of a deal room' and 'Returns user_id, email, role, and per-folder permissions.' This is a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs list_room_members 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_room_members, this is the rule to start with:
list_room_members 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_room_members call is checked against it from then on.
Questions about list_room_members
Use this to list members of a deal room when checking who has access before granting more or before sharing sensitive content. Returns user_id, email, role, and per-folder permissions. 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_room_members: 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_room_members 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_room_members 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_room_members. 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_room_members 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