MCP Server Policy

CONFLUENT KAFKA MCP POLICY

Enforce policies on every tool call to the Confluent Kafka MCP Server. 46 tools listed, categorised, and ready for rules.

@confluentinc/mcp-confluent 28 read 18 write 46 tools total
confluent-kafka streaming kafka flink data-pipeline

GET STARTED

Download this policy scaffold and add your rules. Intercept enforces them on every tool call before it reaches Confluent Kafka.

terminal

# Download policy scaffold

curl -o confluent-kafka.yaml https://raw.githubusercontent.com/policylayer/intercept/main/policies/confluent-kafka.yaml

# Run with Intercept

intercept --policy confluent-kafka.yaml -- npx -y @@confluentinc/mcp-confluent

Server documentation: https://github.com/confluentinc/mcp-confluent

READ TOOLS

28

WRITE TOOLS

11

DESTRUCTIVE TOOLS

7

POLICY YAML

This scaffold lists every tool with empty rules. Add conditions — rate limits, argument validation, deny rules — then deploy with Intercept.

confluent-kafka.yaml
version: "1"
description: "Policy for @confluentinc/mcp-confluent"
default: "allow"
tools:
    list-topics:
        rules: []
    search-topics-by-tag:
        rules: []
    search-topics-by-name:
        rules: []
    get-topic-config:
        rules: []
    list-tags:
        rules: []
    list-clusters:
        rules: []
    list-environments:
        rules: []
    read-environment:
        rules: []
    list-schemas:
        rules: []
    list-connectors:
        rules: []
    read-connector:
        rules: []
    consume-messages:
        rules: []
    list-flink-statements:
        rules: []
    read-flink-statement:
        rules: []
    list-flink-catalogs:
        rules: []
    list-flink-databases:
        rules: []
    list-flink-tables:
        rules: []
    describe-flink-table:
        rules: []
    get-flink-table-info:
        rules: []
    get-flink-statement-exceptions:
        rules: []
    get-flink-statement-profile:
        rules: []
    check-flink-statement-health:
        rules: []
    detect-flink-statement-issues:
        rules: []
    list-tableflow-regions:
        rules: []
    list-tableflow-topics:
        rules: []
    read-tableflow-topic:
        rules: []
    list-tableflow-catalog-integrations:
        rules: []
    read-tableflow-catalog-integration:
        rules: []
    create-topics:
        rules: []
    produce-message:
        rules: []
    create-connector:
        rules: []
    create-flink-statement:
        rules: []
    create-topic-tags:
        rules: []
    add-tags-to-topic:
        rules: []
    alter-topic-config:
        rules: []
    create-tableflow-topic:
        rules: []
    update-tableflow-topic:
        rules: []
    create-tableflow-catalog-integration:
        rules: []
    update-tableflow-catalog-integration:
        rules: []
    delete-topics:
        rules: []
    delete-connector:
        rules: []
    delete-flink-statements:
        rules: []
    delete-tag:
        rules: []
    remove-tag-from-entity:
        rules: []
    delete-tableflow-topic:
        rules: []
    delete-tableflow-catalog-integration:
        rules: []

FREQUENTLY ASKED QUESTIONS

What tools does the Confluent Kafka MCP server expose?

The Confluent Kafka MCP Server exposes 46 tools across 3 categories: Read, Write, Destructive. Each tool can be individually controlled with Intercept policies.

How do I enforce policies on Confluent Kafka?

Download the policy scaffold, add rules (rate limits, argument validation, deny rules), then run Intercept as a proxy in front of the Confluent Kafka MCP server. Every tool call is evaluated against your YAML policy before execution.

Is the Confluent Kafka policy free to use?

Yes. All Intercept policies are open source under the Apache 2.0 licence. Download, modify, and deploy without restrictions.

ENFORCE POLICIES ON CONFLUENT KAFKA

Open source. One binary. Zero dependencies.