start_db_node · OCI MCP Server MCP: Risk & Policy

WHAT IT DOES

What start_db_node does on OCI MCP Server

AI agents invoke start_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 start_db_node needs a policy

This tool executes an operation that starts a database node in Oracle Cloud Infrastructure. Starting a database node is an executable action that initiates external services and changes system state; it is not merely reading data (Read), creating reversible records (Write), or permanently destroying resources (Destructive). The effect depends on the arguments (which node/database to start).

From the tool's definition start_db_node - tool name indicates starting/powering on a database node, which triggers external infrastructure operations in OCI with effects dependent on which node is targeted

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

start_db_node Rate-limited

start_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": {
    "start_db_node": {
      "limits": [
        {
          "counter": "start_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 start_db_node

What does the start_db_node tool do? +

start_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 start_db_node? +

Register the OCI MCP Server MCP server in PolicyLayer and add a rule for start_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 start_db_node? +

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

Can I rate-limit start_db_node? +

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

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

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