Create a Kafka topic with configurable partitions, replication, retention, and cleanup policy.
AI agents use kafka_topic_create to create or update resources in RedisNexus — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your RedisNexus environment.
This tool creates new Kafka topics, which is a reversible Write operation (topics can be deleted). However, it carries medium severity because misconfiguration of production topics could impact data pipeline availability and integrity. The tool does not execute arbitrary code, delete data, or move money, so Write is the appropriate category rather than Execute or higher.
From the tool's definition Tool name 'kafka_topic_create' and description 'Create a Kafka topic' indicates irreversible creation of infrastructure resources.
Attacks that exploit this kind of access
Create a Kafka topic with configurable partitions, replication, retention, and cleanup policy. It is categorised as a Write tool in the RedisNexus MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the RedisNexus MCP server in PolicyLayer and add a rule for kafka_topic_create: 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.
kafka_topic_create 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_topic_create 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_topic_create. 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_topic_create 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.
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 →