Query OBProxy cluster detail This interface is used to query OBProxy cluster detail information. The caller must be authenticated through OCP application service. Args: cluster_id: The ID of the OBProxy cluster Returns: Dictionary containing OBProxy cluster detail information
AI agents call get_oceanbase_obproxy_cluster_detail 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 OBProxy cluster configuration and detail information. It takes a cluster_id parameter and returns data without modifying, deleting, or executing any operations. The authentication requirement and restricted access to OCP application service users mitigates exposure, but the core function remains a read-only query operation.
From the tool's definition Tool name contains 'get_' and description states 'Query OBProxy cluster detail' with 'Returns: Dictionary containing OBProxy cluster detail information'. These clearly indicate a retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access get_oceanbase_obproxy_cluster_detail 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_obproxy_cluster_detail:
{
"version": "1",
"default": "deny",
"tools": {
"get_oceanbase_obproxy_cluster_detail": {}
}
}get_oceanbase_obproxy_cluster_detail 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 OBProxy cluster detail This interface is used to query OBProxy cluster detail information. The caller must be authenticated through OCP application service. Args: cluster_id: The ID of the OBProxy cluster Returns: Dictionary containing OBProxy cluster detail information. 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_obproxy_cluster_detail: 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_obproxy_cluster_detail 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_obproxy_cluster_detail 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_obproxy_cluster_detail. 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_obproxy_cluster_detail 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.