Generate performance report Generate cluster performance report. The caller must have read and write permissions for the specified cluster. Args: cluster_id: Target OceanBase cluster ID (required) start_snapshot_id: Start snapshot ID for the report (required) end_snapshot_id: End snapshot ID for ...
AI agents use create_oceanbase_performance_report to create or update resources in Mcp Oceanbase — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Oceanbase environment.
This tool creates a new report artifact in the OceanBase cluster, which is a Write operation (reversible resource creation). While it requires cluster read/write permissions, the action itself is creating performance analysis data rather than executing arbitrary code or destructively removing data.
From the tool's definition The tool generates and creates a performance report (returning a report ID and status), requiring 'read and write permissions' and storing results ('Report unique ID', 'status').
Documented attack patterns abuse exactly the kind of access create_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 create_oceanbase_performance_report:
{
"version": "1",
"default": "deny",
"tools": {
"create_oceanbase_performance_report": {
"limits": [
{
"counter": "create_oceanbase_performance_report_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_oceanbase_performance_report stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Generate performance report Generate cluster performance report. The caller must have read and write permissions for the specified cluster. Args: cluster_id: Target OceanBase cluster ID (required) start_snapshot_id: Start snapshot ID for the report (required) end_snapshot_id: End snapshot ID for the report (required) name: Report name (required) Returns: Dictionary containing report information including: - id: Report unique ID - clusterName: Cluster name - status: Report status (CREATING/SUCCESSFUL/FAILED) - taskInstanceId: Associated task instance ID. It is categorised as a Write tool in the Mcp Oceanbase MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Oceanbase MCP server in PolicyLayer and add a rule for create_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.
create_oceanbase_performance_report is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_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 create_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.
create_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.