Get OceanBase cluster OBServer list This interface is used to query all OBServer node information of the target OceanBase cluster. The caller must have at least read-only permissions on the target OceanBase cluster. Args: cluster_id: The ID of the target cluster region_name: Query OceanBase serve...
AI agents call get_oceanbase_cluster_servers 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 performs a read-only query operation to retrieve OBServer node information from an OceanBase cluster. It has no side effects, does not modify or delete data, and requires read-only permissions. It falls squarely into the Read category with low severity since it only retrieves cluster infrastructure information.
From the tool's definition Tool description states it is used to 'query all OBServer node information' and 'The caller must have at least read-only permissions'.
Documented attack patterns abuse exactly the kind of access get_oceanbase_cluster_servers 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_cluster_servers:
{
"version": "1",
"default": "deny",
"tools": {
"get_oceanbase_cluster_servers": {}
}
}get_oceanbase_cluster_servers 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.
Get OceanBase cluster OBServer list This interface is used to query all OBServer node information of the target OceanBase cluster. The caller must have at least read-only permissions on the target OceanBase cluster. Args: cluster_id: The ID of the target cluster region_name: Query OceanBase servers in the specified region (optional) idc_name: Query OceanBase servers in the specified IDC (optional) Returns: Dictionary containing server information 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_cluster_servers: 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_cluster_servers 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_cluster_servers 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_cluster_servers. 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_cluster_servers 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.