List all members of a Clink group. Shows member names, roles, and when they joined.
AI agents call list_members to retrieve information from Clink MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries group membership information without creating, modifying, deleting, executing code, or triggering external operations. It has minimal blast radius if misused by an AI agent, as viewing member metadata poses no security or operational risk.
From the tool's definition Tool name 'list_members' and description explicitly states it 'List[s] all members' and 'Shows member names, roles, and when they joined' — purely a data retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
List all members of a Clink group. Shows member names, roles, and when they joined. It is categorised as a Read tool in the Clink MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Clink MCP Server MCP server in PolicyLayer and add a rule for list_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 Clink MCP Server. Nothing to install.
list_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_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_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_members is provided by the Clink MCP Server MCP server (voxos-ai-inc/clink-mcp-server-python). 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 →