AI agents use write_events_to_stream to create or update resources in KurrentDB MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your KurrentDB MCP Server environment.
Writing events to a stream creates or modifies data in KurrentDB. This is reversible (events can be read or processed differently) but represents a material change to the event store. It falls under Write category rather than Execute because it is a direct data creation operation, not a code execution or command trigger.
From the tool's definition Tool name 'write_events_to_stream' explicitly indicates writing/creating events to a stream. Server description confirms 'write events' capability. No description provided for the tool itself, but the name is clear and unambiguous.
Documented attack patterns abuse exactly the kind of access write_events_to_stream gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and KurrentDB MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for write_events_to_stream:
{
"version": "1",
"default": "deny",
"tools": {
"write_events_to_stream": {
"limits": [
{
"counter": "write_events_to_stream_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}write_events_to_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.
write_events_to_stream. It is categorised as a Write tool in the KurrentDB MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the KurrentDB MCP Server MCP server in PolicyLayer and add a rule for write_events_to_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 KurrentDB MCP Server. Nothing to install.
write_events_to_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 write_events_to_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 write_events_to_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.
write_events_to_stream is provided by the KurrentDB MCP Server MCP server (kurrent-io/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from KurrentDB MCP Server, 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.
8 KurrentDB MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.