巡检集群，并返回巡检报告 :param cluster_name: 集群配置文件名前缀，可选。如 ob_test 表示使用 ~/.obdiag/ob_test.yml。不传则使用默认 config.yml :return: 指令执行的输出结果
AI agents invoke obdiag_check_run to trigger actions in Mcp Oceanbase. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool runs a diagnostic inspection/check operation against a cluster and executes commands, returning their output. It is a read-oriented diagnostic scan but involves executing external commands/scripts against the cluster infrastructure, placing it in the Execute category. The blast radius is medium as it only reads/inspects but does interact with live cluster infrastructure.
From the tool's definition 巡检集群，并返回巡检报告 (Inspect/check the cluster and return inspection report); 'call_obshell_sdk' sibling suggests external operations; ':return: 指令执行的输出结果' (returns command execution output)
Documented attack patterns abuse exactly the kind of access obdiag_check_run 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_check_run:
{
"version": "1",
"default": "deny",
"tools": {
"obdiag_check_run": {
"limits": [
{
"counter": "obdiag_check_run_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}obdiag_check_run stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
巡检集群，并返回巡检报告 :param cluster_name: 集群配置文件名前缀，可选。如 ob_test 表示使用 ~/.obdiag/ob_test.yml。不传则使用默认 config.yml :return: 指令执行的输出结果. It is categorised as a Execute tool in the Mcp Oceanbase MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Oceanbase MCP server in PolicyLayer and add a rule for obdiag_check_run: 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.
obdiag_check_run is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the obdiag_check_run 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.
Set action: deny in the PolicyLayer policy for obdiag_check_run. 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.
obdiag_check_run 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.
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.