Query events from a stream with optional pagination and time range filters
AI agents call conduit_list_events to retrieve information from Conduit MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries existing events from a stream with optional filtering and pagination—classic read-only data access. It has no capability to create, modify, delete, execute code, or commit financial transactions. The blast radius of misuse is limited to information disclosure (accessing events a user shouldn't see), making it low severity.
From the tool's definition Tool name 'conduit_list_events' and description 'Query events from a stream with optional pagination and time range filters' indicate retrieval of data with no modification or deletion capabilities. The use of 'query' and 'filters' are read-only operations.
Attacks that exploit this kind of access
Query events from a stream with optional pagination and time range filters. It is categorised as a Read tool in the Conduit MCP MCP Server, which means it retrieves data without modifying state.
Register the Conduit MCP server in PolicyLayer and add a rule for conduit_list_events: 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 Conduit MCP. Nothing to install.
conduit_list_events 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 conduit_list_events 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 conduit_list_events. 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.
conduit_list_events is provided by the Conduit MCP server (useconduit/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 →