Query performance report Query cluster performance report. The caller must have read and write permissions for the specified cluster. Note: This endpoint returns binary HTML content that can be saved as an HTML file. Args: cluster_id: Target OceanBase cluster ID (required) report_id: Performance ...
AI agents call get_oceanbase_performance_report 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 existing performance report data from an OceanBase cluster. It has read-only semantics—it fetches a pre-generated HTML report without modifying, creating, or destructively altering any data. The requirement for write permissions is unusual but appears to be a permission check rather than an indication of write operations.
From the tool's definition Tool description states 'Query performance report' and 'Query cluster performance report'. Returns 'Binary HTML content' that is read-only output. No modification, deletion, or execution of arbitrary code is performed.
Documented attack patterns abuse exactly the kind of access get_oceanbase_performance_report 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_performance_report:
{
"version": "1",
"default": "deny",
"tools": {
"get_oceanbase_performance_report": {}
}
}get_oceanbase_performance_report 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 performance report Query cluster performance report. The caller must have read and write permissions for the specified cluster. Note: This endpoint returns binary HTML content that can be saved as an HTML file. Args: cluster_id: Target OceanBase cluster ID (required) report_id: Performance report ID (required) directory: The directory where the HTML report is saved (required), and the absolute path is not empty Returns: Binary HTML content. 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_performance_report: 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_performance_report 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_performance_report 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_performance_report. 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_performance_report 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.