Low Risk

obdiag_gather_log

obdiag_gather_log

How to control obdiag_gather_log ↓

AI agents call obdiag_gather_log 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

The name implies a diagnostic log gathering operation (read/fetch logs). No description is provided to confirm side effects. Logs gathering is typically a Read operation, but without a description, confidence is reduced. Severity is medium because log data may contain sensitive information.

From the tool's definition Tool name 'obdiag_gather_log' suggests gathering/collecting logs, which is a read operation. Description is empty, lowering confidence.

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

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

obdiag_gather_log 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 obdiag_gather_log tool do? +

obdiag_gather_log. 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 obdiag_gather_log? +

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

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

Can I rate-limit obdiag_gather_log? +

Yes. Add a rate_limit block to the obdiag_gather_log 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 obdiag_gather_log completely? +

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

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