Query monitor metric description information This interface is used to query the description information of metrics currently provided by OCP application. Users can use these descriptions to further query corresponding monitoring data. The caller must be authenticated through OCP application serv...
AI agents call get_oceanbase_metric_groups 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 against OCP monitoring metadata. It retrieves metric group descriptions to help users understand what metrics are available for further querying. There are no side effects, data modifications, deletions, or external code execution. The operation is purely informational and requires authentication but poses minimal risk if misused by an AI agent.
From the tool's definition Tool name includes 'get_' and description states 'Query monitor metric description information' and 'query the description information of metrics'. The interface retrieves metadata about available metrics without modifying, deleting, or executing operations.
Documented attack patterns abuse exactly the kind of access get_oceanbase_metric_groups 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_metric_groups:
{
"version": "1",
"default": "deny",
"tools": {
"get_oceanbase_metric_groups": {}
}
}get_oceanbase_metric_groups 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 monitor metric description information This interface is used to query the description information of metrics currently provided by OCP application. Users can use these descriptions to further query corresponding monitoring data. The caller must be authenticated through OCP application service. Args: type: Metric type: TOP or NORMAL scope: Metric scope: CLUSTER, TENANT, HOST, or OBPROXY page: Pagination page number, starting from 1, default: 1 size: Pagination size, default: 10, maximum: 2000 sort: Sorting rule (optional) target: Metric metadata type: OBCLUSTER or OBPROXY (optional) target_id: Metric metadata ID (optional) Returns: Dictionary containing metric group list and pagination 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_metric_groups: 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_metric_groups 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_metric_groups 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_metric_groups. 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_metric_groups 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.