start_db_system · OCI MCP Server MCP: Risk & Policy

WHAT IT DOES

What start_db_system does on OCI MCP Server

AI agents invoke start_db_system 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_system needs a policy

Starting a database system executes an operation with external effects (VM/service startup, resource allocation, potential billing impact). It is not merely Read (no data retrieval), Write (not creating/modifying data objects), or Destructive (reversible—can be stopped). It is Execute because it triggers a cloud operation whose effects depend on which database system is targeted.

From the tool's definition Tool named 'start_db_system' with empty description. Based on server context enabling management of 'database systems' through OCI, this tool starts (initiates/boots) a database system—a state-changing operation that triggers external infrastructure.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

start_db_system Rate-limited

start_db_system 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_system": {
      "limits": [
        {
          "counter": "start_db_system_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_system

What does the start_db_system tool do? +

start_db_system. 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_system? +

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

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

Can I rate-limit start_db_system? +

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

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

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