members_list
List members of an organization with their roles and status.
This record as markdown: /tools/com-servicialo-mcp-server/members-list.md
What members_list does on Servicialo
AI agents call members_list to retrieve information from Servicialo without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
apiKey | string | — | |
orgSlug | string | Yes |
Parameters from the server's own tool schema.
Why members_list is rated Low
This tool retrieves and queries organizational membership data without modifying, creating, deleting, or executing any operations. It falls squarely within the Read category as a listing/fetch operation. Severity is low because membership lists are typically non-sensitive organizational information, and misuse carries minimal blast radius.
From the tool's definition Tool name 'members_list' and description 'List members of an organization with their roles and status' indicate a pure retrieval operation with no side effects.
Risk signalsHandles credentials or secrets (apiKey)
Attacks that exploit this kind of access
The rule that runs members_list safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Servicialo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For members_list, this is the rule to start with:
members_list 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 Servicialo, apply this rule, and every members_list call is checked against it from then on.
Questions about members_list
List members of an organization with their roles and status. It is categorised as a Read tool in the Servicialo MCP Server, which means it retrieves data without modifying state.
members_list accepts 2 parameters: apiKey, orgSlug. Required: orgSlug. The full parameter table on this page comes from the server's own tool schema.
Register the Servicialo MCP server in PolicyLayer and add a rule for members_list: 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 Servicialo. Nothing to install.
members_list 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 members_list 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 members_list. 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.
members_list is provided by the Servicialo MCP server (@servicialo/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Servicialo, and thousands of servers like it.
This server
Across the catalogue