kafka_produce · RedisNexus MCP: Risk & Policy

WHAT IT DOES

What kafka_produce does on RedisNexus

AI agents invoke kafka_produce to trigger actions in RedisNexus. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why kafka_produce needs a policy

Producing messages to Kafka is an Execute action because it runs an operation with external side effects that depend on user-supplied arguments (topic, message content, key, headers, partition). While not destructive or financial, misuse could inject malicious messages into production systems, disrupt message streams, or trigger downstream processes.

From the tool's definition Tool description states it 'Produce messages to a Kafka topic' - this is an action that triggers external operations (message production to a message queue) whose effects depend on the message content and topic arguments provided.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

kafka_produce Rate-limited

kafka_produce stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "kafka_produce": {
      "limits": [
        {
          "counter": "kafka_produce_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches RedisNexus, so you can run agents against it safely.

FAQ

Questions about kafka_produce

What does the kafka_produce tool do? +

Produce messages to a Kafka topic with optional key, headers, and partition. It is categorised as a Execute tool in the RedisNexus MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on kafka_produce? +

Register the RedisNexus MCP server in PolicyLayer and add a rule for kafka_produce: 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 RedisNexus. Nothing to install.

What risk level is kafka_produce? +

kafka_produce is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit kafka_produce? +

Yes. Add a rate_limit block to the kafka_produce 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.

How do I block kafka_produce completely? +

Set action: deny in the PolicyLayer policy for kafka_produce. 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.

What MCP server provides kafka_produce? +

kafka_produce is provided by the RedisNexus MCP server (rajkumar-madhu/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.