Low Risk

obdiag_cluster_list

列出可用的集群配置名称列表,用于在其他工具中指定 cluster_name 参数 返回 ~/.obdiag/ 目录下所有 .yml 配置文件的文件名前缀(不含 .yml),已排除 ai.yml 例如:ob_test.yml 对应 cluster_name=ob_test,config.yml 对应 cluster_name=config :return: 可用集群名称列表,格式为逗号分隔的字符串

How to control obdiag_cluster_list ↓

AI agents call obdiag_cluster_list to retrieve information from Mcp Oceanbase without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This is a read-only operation that retrieves metadata about available cluster configurations. It queries the filesystem to enumerate configuration options but does not modify, execute, delete, or create any data. The blast radius is minimal as it only exposes configuration names that would be needed to use other tools.

From the tool's definition Tool lists available cluster configuration names from ~/.obdiag/ directory by reading .yml file names. The description explicitly states it 'returns' and 'lists' configuration filenames without modification.

Documented attack patterns abuse exactly the kind of access obdiag_cluster_list gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Oceanbase, and nothing reaches the server without passing your rules. This is the rule we recommend for obdiag_cluster_list:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "obdiag_cluster_list": {}
  }
}

obdiag_cluster_list is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Mcp Oceanbase — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the obdiag_cluster_list tool do? +

列出可用的集群配置名称列表,用于在其他工具中指定 cluster_name 参数 返回 ~/.obdiag/ 目录下所有 .yml 配置文件的文件名前缀(不含 .yml),已排除 ai.yml 例如:ob_test.yml 对应 cluster_name=ob_test,config.yml 对应 cluster_name=config :return: 可用集群名称列表,格式为逗号分隔的字符串. It is categorised as a Read tool in the Mcp Oceanbase MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on obdiag_cluster_list? +

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

What risk level is obdiag_cluster_list? +

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

Can I rate-limit obdiag_cluster_list? +

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

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

obdiag_cluster_list is provided by the Mcp Oceanbase MCP server (oceanbase/awesome-oceanbase-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Oceanbase tool call.

Deterministic rules across all 134 Mcp Oceanbase tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

134 Mcp Oceanbase tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.