Critical Risk →

delete_kafka_connector

Deletes a Kafka connector.

How to control delete_kafka_connector ↓

What delete_kafka_connector does on Lenses MCP Server

AI agents call delete_kafka_connector to permanently remove resources in Lenses MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why delete_kafka_connector needs a policy

Deleting a Kafka connector terminates data pipelines and cannot be undone without manual recreation. This is irreversible infrastructure modification with potential operational impact (data flow interruption). While not data deletion per se, it destroys connector state/configuration.

From the tool's definition Tool name explicitly contains 'delete' and description states 'Deletes a Kafka connector.' Deletion of connectors is irreversible—once removed, the connector configuration and its operational state are lost.

Documented attack patterns abuse exactly the kind of access delete_kafka_connector gives an agent:

How to control delete_kafka_connector

PolicyLayer is an MCP gateway — it sits between your AI agents and Lenses MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_kafka_connector:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_kafka_connector"
  ]
}

delete_kafka_connector disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Lenses MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about delete_kafka_connector

What does the delete_kafka_connector tool do? +

Deletes a Kafka connector. It is categorised as a Destructive tool in the Lenses MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_kafka_connector? +

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

What risk level is delete_kafka_connector? +

delete_kafka_connector is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_kafka_connector? +

Yes. Add a rate_limit block to the delete_kafka_connector 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 delete_kafka_connector completely? +

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

delete_kafka_connector is provided by the Lenses MCP Server MCP server (lensesio/lenses-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Lenses MCP Server tool call.

Start from Lenses 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.

42 Lenses MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.