Get resource capacity from oceanbase. You need to be sys tenant to get resource capacity.
AI agents call get_resource_capacity 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 system resource capacity information from OceanBase. It performs a query operation that reads data without side effects, making it a Read category tool. The requirement to be 'sys tenant' indicates access control but does not change the nature of the operation. Severity is low because retrieving capacity metrics poses minimal risk even if misused—it provides informational data only.
From the tool's definition Tool name 'get_resource_capacity' and description 'Get resource capacity from oceanbase' indicates a retrieval operation with no modification or deletion of data.
Documented attack patterns abuse exactly the kind of access get_resource_capacity 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_resource_capacity:
{
"version": "1",
"default": "deny",
"tools": {
"get_resource_capacity": {}
}
}get_resource_capacity 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 resource capacity from oceanbase. You need to be sys tenant to get resource capacity. 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_resource_capacity: 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_resource_capacity 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_resource_capacity 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_resource_capacity. 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_resource_capacity 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.