stop_db_system · OCI MCP Server MCP: Risk & Policy

WHAT IT DOES

What stop_db_system does on OCI MCP Server

AI agents invoke stop_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 stop_db_system needs a policy

This tool executes an operation that triggers external effects on OCI resources (stopping a running database system). While not permanently destructive (the system can be restarted), it is an Execute action that halts availability and can impact production services.

From the tool's definition Tool name 'stop_db_system' performs a state-changing action on a database system resource in OCI. The verb 'stop' indicates triggering an operational state change on infrastructure.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

stop_db_system Rate-limited

stop_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": {
    "stop_db_system": {
      "limits": [
        {
          "counter": "stop_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 stop_db_system

What does the stop_db_system tool do? +

stop_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 stop_db_system? +

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

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

Can I rate-limit stop_db_system? +

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

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

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