cluster_metadata

Obtiene metadata completa del cluster: brokers, topics, controller. Retorna: cluster_id, brokers[], broker_count, topic_count.

SERVERMCP Framework Personal SOURCEinggerman/mcps

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/inggerman-mcps/cluster-metadata.md

WHAT IT DOES

What cluster_metadata does on MCP Framework Personal

AI agents call cluster_metadata to retrieve information from MCP Framework Personal without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why cluster_metadata is rated Low

This tool retrieves metadata about a Kafka or message broker cluster (brokers, topics, controller information). It performs a read-only query with no side effects, mutations, or destructive actions. The blast radius is medium because exposing cluster topology and broker configuration could enable reconnaissance for further attacks, but the tool itself does not execute code, modify data, or cause financial impact.

From the tool's definition Tool name 'cluster_metadata' and description 'Obtiene metadata completa del cluster: brokers, topics, controller.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs cluster_metadata safely

PolicyLayer is an MCP gateway: it sits between your AI agents and MCP Framework Personal, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For cluster_metadata, this is the rule to start with:

cluster_metadata Allowed

cluster_metadata is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "cluster_metadata": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect MCP Framework Personal, apply this rule, and every cluster_metadata call is checked against it from then on.

FAQ

Questions about cluster_metadata

What does the cluster_metadata tool do? +

Obtiene metadata completa del cluster: brokers, topics, controller. Retorna: cluster_id, brokers[], broker_count, topic_count. It is categorised as a Read tool in the MCP Framework Personal MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on cluster_metadata? +

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

What risk level is cluster_metadata? +

cluster_metadata is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit cluster_metadata? +

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

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

cluster_metadata is provided by the MCP Framework Personal MCP server (inggerman/mcps). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on MCP Framework Personal, and thousands of servers like it.

This server

All 811 MCP Framework Personal tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →