Query slow SQL list This interface is used to query slow SQL list. The caller must have read permissions for the specified tenant. Args: cluster_id: Cluster ID (required) tenant_id: Tenant ID (required) start_time: Start time (UTC format: YYYY-MM-DDThh:mm:ssZ) (required) end_time: End time (UTC f...
AI agents call get_oceanbase_tenant_slow_sql 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.
This tool retrieves and queries diagnostic/monitoring data about slow SQL queries from OceanBase. It has no side effects, does not execute code, and does not modify data. The requirement for read permissions confirms it is a read-only operation. The low severity reflects that querying logs/metrics poses minimal risk even if misused by an agent.
From the tool's definition Tool name is 'get_oceanbase_tenant_slow_sql' and description states 'Query slow SQL list'. The interface explicitly requires 'read permissions' and all parameters are for filtering/querying existing data (cluster_id, tenant_id, start_time, end_time,…
Documented attack patterns abuse exactly the kind of access get_oceanbase_tenant_slow_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 get_oceanbase_tenant_slow_sql:
{
"version": "1",
"default": "deny",
"tools": {
"get_oceanbase_tenant_slow_sql": {}
}
}get_oceanbase_tenant_slow_sql is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Query slow SQL list This interface is used to query slow SQL list. The caller must have read permissions for the specified tenant. Args: cluster_id: Cluster ID (required) tenant_id: Tenant ID (required) start_time: Start time (UTC format: YYYY-MM-DDThh:mm:ssZ) (required) end_time: End time (UTC format: YYYY-MM-DDThh:mm:ssZ) (required) server_id: Query SQL performance on specified OceanBase server (optional) inner: Whether it's internal SQL (optional) sql_text: SQL text keyword (case-insensitive) (optional) filter_expression: Filter expression, all fields referenced by @ (optional) limit: Number of TOP results to return (optional) sql_text_length: Maximum length of returned SQL text (optional) Returns: Dictionary containing slow SQL list. It is categorised as a Read tool in the Mcp Oceanbase MCP Server, which means it retrieves data without modifying state.
Register the Mcp Oceanbase MCP server in PolicyLayer and add a rule for get_oceanbase_tenant_slow_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.
get_oceanbase_tenant_slow_sql is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_oceanbase_tenant_slow_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 get_oceanbase_tenant_slow_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.
get_oceanbase_tenant_slow_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.