MCP Tool Reference Critical Risk

delete-connector

Delete an existing connector

Part of the Confluent Kafka MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

WHEN AI AGENTS USE THIS TOOL

AI agents may call delete-connector to permanently remove or destroy resources in Confluent Kafka. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. Intercept blocks destructive tools by default and requires explicit human approval before enabling them.

WHY ENFORCE A POLICY ON DELETE-CONNECTOR

Without a policy, an AI agent could call delete-connector in a loop, permanently destroying resources in Confluent Kafka. There is no undo for destructive operations. Intercept blocks this tool by default and only allows it when a human explicitly approves the action.

RECOMMENDED POLICY

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

confluent-kafka.yaml
tools:
  delete-connector:
    rules:
      - action: deny
        reason: "Blocked by default — enable with approval"

See the full Confluent Kafka policy for all 46 tools.

DETAILS

Tool Name

delete-connector

Category

Destructive

Risk Level

Critical

MORE CONFLUENT KAFKA TOOLS

View all 46 tools →

SIMILAR DESTRUCTIVE TOOLS ON OTHER SERVERS

RELATED READING

FREQUENTLY ASKED QUESTIONS

What does the delete-connector tool do?

Delete an existing connector. It is categorised as a Destructive tool in the Confluent Kafka 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-connector?

Add a rule in your Intercept YAML policy under the tools section for delete-connector. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Confluent Kafka MCP server.

What risk level is delete-connector?

delete-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-connector?

Yes. Add a rate_limit block to the delete-connector rule in your Intercept 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-connector completely?

Set action: deny in the Intercept policy for delete-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-connector?

delete-connector is provided by the Confluent Kafka MCP server (@confluentinc/mcp-confluent). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

ENFORCE POLICIES ON CONFLUENT KAFKA

Open source. One binary. Zero dependencies.