Create a new data stream. Just send a name — schema is auto-detected from the first event.
AI agents use conduit_create_stream to create or update resources in Conduit MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Conduit MCP environment.
This tool creates a new resource (a data stream) which is a reversible write operation. It does not delete, execute arbitrary code, move money, or trigger uncontrolled external operations. The blast radius is moderate: an agent could create many streams or pollute the namespace, but streams can be deleted and are typically isolated.
From the tool's definition Tool description states 'Create a new data stream' — a direct creation action that modifies the system state by adding a new stream resource.
Attacks that exploit this kind of access
Create a new data stream. Just send a name — schema is auto-detected from the first event. It is categorised as a Write tool in the Conduit MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Conduit MCP server in PolicyLayer and add a rule for conduit_create_stream: 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_create_stream is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the conduit_create_stream 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_create_stream. 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_create_stream 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 →