Query the last inspection result of a specified inspection item This interface queries the last inspection result of a specified inspection item based on conditions such as inspection object type, inspection scenario, and inspection object ID (optional). The caller must be authenticated through O...
AI agents call get_oceanbase_inspection_item_last_result 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 inspection results based on query parameters (item_id, tag_id, inspection object type/ID). It is fundamentally a read operation that queries and returns diagnostic/inspection data without modifying, deleting, or executing operations.
From the tool's definition Query the last inspection result of a specified inspection item
Documented attack patterns abuse exactly the kind of access get_oceanbase_inspection_item_last_result 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_item_last_result:
{
"version": "1",
"default": "deny",
"tools": {
"get_oceanbase_inspection_item_last_result": {}
}
} get_oceanbase_inspection_item_last_result 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 the last inspection result of a specified inspection item This interface queries the last inspection result of a specified inspection item based on conditions such as inspection object type, inspection scenario, and inspection object ID (optional). The caller must be authenticated through OCP application service. Args: item_id: Inspection item ID (required) 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. 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_inspection_item_last_result: 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_inspection_item_last_result 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_inspection_item_last_result 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_inspection_item_last_result. 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_inspection_item_last_result 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.