Get database list This interface is used to get the database list of a tenant. The caller must be authenticated through OCP application service. The caller must have read permissions on the specified tenant. Args: cluster_id: The ID of the cluster tenant_id: The ID of the tenant Returns: Dictiona...
AI agents call get_oceanbase_tenant_databases 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 metadata about databases belonging to a tenant. It requires read permissions and returns data without creating, modifying, or deleting any resources. The operation is non-destructive and read-only in nature, fitting the Read category with low severity due to limited blast radius if misused by an AI agent.
From the tool's definition Tool name contains 'get_' and description states 'Get database list' — a retrieval operation with no modification or deletion. Returns a 'Dictionary containing database list' with no side effects mentioned.
Documented attack patterns abuse exactly the kind of access get_oceanbase_tenant_databases 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_databases:
{
"version": "1",
"default": "deny",
"tools": {
"get_oceanbase_tenant_databases": {}
}
}get_oceanbase_tenant_databases 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 database list This interface is used to get the database list of a tenant. The caller must be authenticated through OCP application service. The caller must have read permissions on the specified tenant. Args: cluster_id: The ID of the cluster tenant_id: The ID of the tenant Returns: Dictionary containing database 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_databases: 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_databases 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_databases 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_databases. 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_databases 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.