delete_kafka_user
AI agents call delete_kafka_user to permanently remove resources in Kafka MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool performs account deletion—a fundamentally irreversible action. Even though the description is empty, the name unambiguously indicates removal of user credentials/access, which aligns with the Destructive category (delete, drop, purge). The blast radius is high: an agent misusing this could disable legitimate users' cluster access, disrupt authentication, and cause operational impact.
From the tool's definition Tool name 'delete_kafka_user' explicitly indicates irreversible deletion of a Kafka user account. The verb 'delete' combined with 'kafka_user' denotes a destructive operation that cannot be undone.
Attacks that exploit this kind of access
delete_kafka_user. It is categorised as a Destructive tool in the Kafka MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Kafka MCP Server MCP server in PolicyLayer and add a rule for delete_kafka_user: 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.
delete_kafka_user is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_kafka_user 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 delete_kafka_user. 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.
delete_kafka_user is provided by the Kafka MCP Server MCP server (jilanisayyad/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 →