AI agents use create_kafka_stream to create or update resources in Mcp Timeplus — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Timeplus environment.
The tool creates a stream (write/create operation), which is reversible (streams can be deleted). The empty description reduces confidence slightly, but the name clearly indicates data creation. Severity is medium because creating streams in a streaming database could have downstream effects on data pipelines and processing, though the impact is contained to stream metadata rather than destructive data loss.
From the tool's definition Tool name 'create_kafka_stream' indicates it creates a new stream, which is a write operation that modifies database state by adding a new stream resource.
Documented attack patterns abuse exactly the kind of access create_kafka_stream gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Timeplus, and nothing reaches the server without passing your rules. This is the rule we recommend for create_kafka_stream:
{
"version": "1",
"default": "deny",
"tools": {
"create_kafka_stream": {
"limits": [
{
"counter": "create_kafka_stream_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_kafka_stream stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
create_kafka_stream. It is categorised as a Write tool in the Mcp Timeplus MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Timeplus MCP server in PolicyLayer and add a rule for create_kafka_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 Mcp Timeplus. Nothing to install.
create_kafka_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 create_kafka_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 create_kafka_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.
create_kafka_stream is provided by the Mcp Timeplus MCP server (timeplus-io/mcp-timeplus). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Timeplus, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
7 Mcp Timeplus tools catalogued and risk-classified — across an index of 43,000+ MCP servers.