Low Risk

get_oceanbase_inspection_report_info

Get the last inspection result of a specific object This interface queries the last inspection result of objects that meet the conditions based on inspection object type, inspection scenario, and inspection object ID (optional). The caller must be authenticated through OCP application service. Ar...

How to control get_oceanbase_inspection_report_info ↓

AI agents call get_oceanbase_inspection_report_info 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.

Low Risk

This tool retrieves inspection reports and diagnostic information from OceanBase systems. It performs a query operation with no side effects, no data modification, no code execution, and no destructive operations. The security risk is minimal - it exposes monitoring/diagnostic data that would typically be available to authenticated administrators.

From the tool's definition Tool description states 'Get the last inspection result' and 'queries the last inspection result of objects' - both indicate data retrieval with no modification.

Documented attack patterns abuse exactly the kind of access get_oceanbase_inspection_report_info 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_inspection_report_info:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_oceanbase_inspection_report_info": {}
  }
}

get_oceanbase_inspection_report_info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Mcp Oceanbase — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the get_oceanbase_inspection_report_info tool do? +

Get the last inspection result of a specific object This interface queries the last inspection result of objects that meet the conditions based on inspection object type, inspection scenario, and inspection object ID (optional). The caller must be authenticated through OCP application service. Args: tag_id: Inspection scenario ID (required): - 1: Basic inspection - 2: Performance inspection - 3: Deep inspection - 4: Installation inspection object_type: Inspection object type (required): - OB_CLUSTER: Cluster - OB_TENANT: Tenant - HOST: Host - OB_PROXY: OBProxy object_id: Object ID Returns: Dictionary containing inspection result aggregation information. The data includes: - contents: Array of InspectionReportAggrInfo InspectionReportAggrInfo includes: - reportId: Inspection report ID - objectId: Inspection object ID - objectName: Inspection object name - objectType: Inspection object type - tag: Inspection scenario information - startTime: Inspection start time - endTime: Inspection end time - resultList: Array of inspection item results. It is categorised as a Read tool in the Mcp Oceanbase MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_oceanbase_inspection_report_info? +

Register the Mcp Oceanbase MCP server in PolicyLayer and add a rule for get_oceanbase_inspection_report_info: 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.

What risk level is get_oceanbase_inspection_report_info? +

get_oceanbase_inspection_report_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_oceanbase_inspection_report_info? +

Yes. Add a rate_limit block to the get_oceanbase_inspection_report_info 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.

How do I block get_oceanbase_inspection_report_info completely? +

Set action: deny in the PolicyLayer policy for get_oceanbase_inspection_report_info. 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.

What MCP server provides get_oceanbase_inspection_report_info? +

get_oceanbase_inspection_report_info 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.

Enforce policy on every Mcp Oceanbase tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.