Get the time range and total event count for a stream. Useful before starting a backfill.
AI agents call conduit_time_range 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 metadata about a stream (time range and event count) without creating, modifying, deleting, or executing anything. It is a read-only query suitable for inspecting stream properties before other operations. Severity is low because misuse simply returns stale or irrelevant information with no blast radius.
From the tool's definition Tool description states 'Get the time range and total event count for a stream' — a pure query operation with no mutation or side effects. The verb 'Get' and the informational purpose (useful for planning a backfill) confirm retrieval-only behavior.
Attacks that exploit this kind of access
Get the time range and total event count for a stream. Useful before starting a backfill. 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_time_range: 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_time_range 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_time_range 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_time_range. 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_time_range 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 →