Run inspection This interface is used to initiate inspection for specified objects with a specific scenario. The caller must be authenticated through OCP application service. Args: inspection_object_type: Inspection object type (required): - OB_CLUSTER: Cluster - OB_TENANT: Tenant - HOST: Host - ...
AI agents invoke run_oceanbase_inspection to trigger actions in Mcp Oceanbase. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes an inspection process on database infrastructure components rather than simply reading data. While inspections are typically non-destructive, they are active operations that trigger external processes and can impact system performance or state monitoring.
From the tool's definition Tool description states 'Run inspection' and 'initiate inspection for specified objects with a specific scenario.' The interface triggers an inspection operation on OceanBase infrastructure objects (clusters, tenants, hosts, proxies) with defined scenarios,…
Documented attack patterns abuse exactly the kind of access run_oceanbase_inspection 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 run_oceanbase_inspection:
{
"version": "1",
"default": "deny",
"tools": {
"run_oceanbase_inspection": {
"limits": [
{
"counter": "run_oceanbase_inspection_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}run_oceanbase_inspection stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Run inspection This interface is used to initiate inspection for specified objects with a specific scenario. The caller must be authenticated through OCP application service. Args: inspection_object_type: Inspection object type (required): - OB_CLUSTER: Cluster - OB_TENANT: Tenant - HOST: Host - OB_PROXY: OBProxy object_ids: Inspection object IDs in OCP (e.g., cluster ID, tenant ID). Multiple IDs should be provided as a list (required) tag: Scenario tag ID (required): - 1: Basic inspection - 2: Performance inspection - 3: Deep inspection - 4: Installation inspection Returns: Dictionary containing async task information. It is categorised as a Execute tool in the Mcp Oceanbase MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Oceanbase MCP server in PolicyLayer and add a rule for run_oceanbase_inspection: 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.
run_oceanbase_inspection is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the run_oceanbase_inspection 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 run_oceanbase_inspection. 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.
run_oceanbase_inspection 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.