Send a message to a Kafka topic
AI agents use kafka_send_message to create or update resources in Kafka MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Kafka MCP Server environment.
Sending a message to Kafka is a reversible write operation—the message is created and stored, but can be consumed or deleted later. It does not execute arbitrary code, delete data irreversibly, or move money. While message publication could trigger downstream effects depending on what consumers do with the message, the tool itself is fundamentally a write operation (Create).
From the tool's definition Tool description states 'Send a message to a Kafka topic', which creates/adds data to a message queue. This is a write operation that modifies the state of the Kafka topic by appending a message.
Attacks that exploit this kind of access
Send a message to a Kafka topic. It is categorised as a Write tool in the Kafka MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Kafka MCP Server MCP server in PolicyLayer and add a rule for kafka_send_message: 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 Kafka MCP Server. Nothing to install.
kafka_send_message 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 kafka_send_message 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 kafka_send_message. 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.
kafka_send_message is provided by the Kafka MCP Server MCP server (joel-hanson/kafka-mcp-server). 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 →