read-connector
Get information about a 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 call read-connector to retrieve information from Confluent Kafka without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions — but you may still want rate limits to control API costs.
WHY ENFORCE A POLICY ON READ-CONNECTOR
Even though read-connector only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
RECOMMENDED POLICY
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
read-connector:
rules:
- action: allowSee the full Confluent Kafka policy for all 46 tools.
DETAILS
MORE CONFLUENT KAFKA TOOLS
list-topics Read search-topics-by-tag Read search-topics-by-name Read get-topic-config Read list-tags Read list-clusters Read list-environments Read read-environment Read SIMILAR READ TOOLS ON OTHER SERVERS
list_bases Airtable list_tables Airtable list_records Airtable get_record Airtable search_records Airtable search Amplitude RELATED READING
FREQUENTLY ASKED QUESTIONS
What does the read-connector tool do?
Get information about a connector. It is categorised as a Read tool in the Confluent Kafka MCP Server, which means it retrieves data without modifying state.
How do I enforce a policy on read-connector?
Add a rule in your Intercept YAML policy under the tools section for read-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 read-connector?
read-connector is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Can I rate-limit read-connector?
Yes. Add a rate_limit block to the read-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 read-connector completely?
Set action: deny in the Intercept policy for read-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 read-connector?
read-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.