list_manifest_participants_sessions
AI agents call list_manifest_participants_sessions to retrieve information from Nipoppy MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'list_' prefix combined with 'manifest_participants_sessions' indicates this tool retrieves or enumerates metadata about participants and their sessions from the dataset manifest. This is a read-only query operation typical of neuroimaging data browsing interfaces.
From the tool's definition Tool name contains 'list_manifest' which indicates enumeration/retrieval of participant and session data. Sibling tools on this server (get_bids_participants_sessions, get_dataset_info, get_participants_sessions, list_manifest_imaging_participants_sessions,…
Attacks that exploit this kind of access
list_manifest_participants_sessions. It is categorised as a Read tool in the Nipoppy MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Nipoppy MCP Server MCP server in PolicyLayer and add a rule for list_manifest_participants_sessions: 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 Nipoppy MCP Server. Nothing to install.
list_manifest_participants_sessions 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_manifest_participants_sessions 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_manifest_participants_sessions. 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_manifest_participants_sessions is provided by the Nipoppy MCP Server MCP server (nipoppy/mcp). 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 →