This record as markdown: /tools/io-github-heznpc-iconnect/list-participants.md
What list_participants does on Iconnect
AI agents call list_participants to retrieve information from Iconnect without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_participants is rated Low
This tool retrieves information about chat participants without creating, modifying, deleting, or executing any operations. It is a straightforward read operation with minimal security risk—exposure could allow unauthorized viewing of chat participant metadata, but the blast radius is limited to information disclosure.
From the tool's definition Tool name 'list_participants' and description 'List all participants in a specific chat' indicate a query/retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs list_participants safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Iconnect, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_participants, this is the rule to start with:
list_participants 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 Iconnect, apply this rule, and every list_participants call is checked against it from then on.
Questions about list_participants
List all participants in a specific chat. It is categorised as a Read tool in the Iconnect MCP Server, which means it retrieves data without modifying state.
Register the Iconnect MCP server in PolicyLayer and add a rule for list_participants: 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 Iconnect. Nothing to install.
list_participants 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_participants 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_participants. 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_participants is provided by the Iconnect MCP server (iconnect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Iconnect, and thousands of servers like it.
This server
Across the catalogue