在集群指定租户下执行SQL查询，支持各种常见SQL查询语句，如SELECT、SHOW TABLES、SHOW COLUMNS等 Args: query: SQL查询语句 cluster_name: 集群名称，如果提供则会重新配置连接 tenant_name: 租户名称，如果提供则会重新配置连接 database: 数据库名称，默认为oceanbase，也可以为业务数据库 namespace: 命名空间，默认为default Returns: 查询结果
AI agents invoke execute_cluster_sql 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 is classified as Execute rather than Read because: (1) it accepts arbitrary SQL statements as input without restriction mentioned, (2) SQL execution can have side effects beyond read operations (UPDATE, INSERT, DELETE), (3) the blast radius of misuse is significant—an AI agent could unintentionally modify or delete data.
From the tool's definition Tool executes SQL queries ("执行SQL查询") with support for various SQL statements including SELECT, SHOW TABLES, SHOW COLUMNS. The description explicitly states it executes queries ("执行") on a cluster under a specified tenant.
Documented attack patterns abuse exactly the kind of access execute_cluster_sql 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 execute_cluster_sql:
{
"version": "1",
"default": "deny",
"tools": {
"execute_cluster_sql": {
"limits": [
{
"counter": "execute_cluster_sql_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}execute_cluster_sql 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.
在集群指定租户下执行SQL查询，支持各种常见SQL查询语句，如SELECT、SHOW TABLES、SHOW COLUMNS等 Args: query: SQL查询语句 cluster_name: 集群名称，如果提供则会重新配置连接 tenant_name: 租户名称，如果提供则会重新配置连接 database: 数据库名称，默认为oceanbase，也可以为业务数据库 namespace: 命名空间，默认为default Returns: 查询结果. 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 execute_cluster_sql: 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.
execute_cluster_sql 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 execute_cluster_sql 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 execute_cluster_sql. 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.
execute_cluster_sql 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.