MCP Tool Reference Critical Risk

delete-tableflow-catalog-integration

Delete a tableflow catalog integration

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

@confluentinc/mcp-confluent Destructive

WHEN AI AGENTS USE THIS TOOL

AI agents may call delete-tableflow-catalog-integration 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-TABLEFLOW-CATALOG-INTEGRATION

Without a policy, an AI agent could call delete-tableflow-catalog-integration 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-tableflow-catalog-integration:
    rules:
      - action: deny
        reason: "Blocked by default — enable with approval"

See the full Confluent Kafka policy for all 46 tools.

DETAILS

Tool Name

delete-tableflow-catalog-integration

Category

Destructive

MCP Server

Confluent Kafka MCP Server

Risk Level

Critical

MORE CONFLUENT KAFKA TOOLS

delete-topics Destructive
Delete topics with the given names
delete-connector Destructive
Delete an existing connector
delete-flink-statements Destructive
Delete a Flink statement
delete-tag Destructive
Delete a tag definition from Confluent Cloud
remove-tag-from-entity Destructive
Remove tag from an entity in Confluent Cloud
delete-tableflow-topic Destructive
Delete a tableflow topic
list-topics Read
List all topics in the Kafka cluster
search-topics-by-tag Read
List all topics with the specified tag

View all 46 tools →

SIMILAR DESTRUCTIVE TOOLS ON OTHER SERVERS

delete_record Airtable
Remove a record
delete_session Appium
Delete the current session and clean up
appium_uninstallApp Appium
Uninstall an app from the device
deleteCompassComponent Atlassian Rovo
Delete a Compass component
deleteConfluencePage Atlassian Rovo
Delete a Confluence page
delete_resource AWS
Delete AWS resources

RELATED READING

FREQUENTLY ASKED QUESTIONS

What does the delete-tableflow-catalog-integration tool do?

Delete a tableflow catalog integration. 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-tableflow-catalog-integration?

Add a rule in your Intercept YAML policy under the tools section for delete-tableflow-catalog-integration. 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-tableflow-catalog-integration?

delete-tableflow-catalog-integration 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-tableflow-catalog-integration?

Yes. Add a rate_limit block to the delete-tableflow-catalog-integration 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-tableflow-catalog-integration completely?

Set action: deny in the Intercept policy for delete-tableflow-catalog-integration. 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-tableflow-catalog-integration?

delete-tableflow-catalog-integration 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.

VIEW ON GITHUB Full Confluent Kafka policy →