reset_db_node · OCI MCP Server MCP: Risk & Policy

WHAT IT DOES

What reset_db_node does on OCI MCP Server

AI agents invoke reset_db_node to trigger actions in OCI MCP Server. 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.

WHY IT NEEDS A POLICY

Why reset_db_node needs a policy

A 'reset' of a DB node typically triggers a restart or reinitialization of a database node in OCI, which constitutes executing an external operation affecting infrastructure. This is not a simple read or write — it disrupts running services. Without a description, confidence is moderate, but the name strongly implies an Execute-level action.

From the tool's definition Tool name 'reset_db_node' — description is empty and uninformative. The word 'reset' implies restarting or reinitializing a database node, which is an operational action with significant impact.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

reset_db_node Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "reset_db_node": {
      "limits": [
        {
          "counter": "reset_db_node_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches OCI MCP Server, so you can run agents against it safely.

FAQ

Questions about reset_db_node

What does the reset_db_node tool do? +

reset_db_node. It is categorised as a Execute tool in the OCI MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on reset_db_node? +

Register the OCI MCP Server MCP server in PolicyLayer and add a rule for reset_db_node: 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 OCI MCP Server. Nothing to install.

What risk level is reset_db_node? +

reset_db_node is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit reset_db_node? +

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

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

reset_db_node is provided by the OCI MCP Server MCP server (jopsis/mcp-server-oci). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.