High Risk →

oci_adb_start

Start a stopped Autonomous Database

Part of the Oracle Cloud server.

oci_adb_start can trigger actions in Oracle Cloud, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE ORACLE CLOUD →

Free to start. No card required.

AI agents invoke oci_adb_start to trigger processes or run actions in Oracle Cloud. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

oci_adb_start can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. PolicyLayer enforces rate limits and validates arguments to keep execution within safe bounds.

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "oci_adb_start": {
      "limits": [
        {
          "counter": "oci_adb_start_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full Oracle Cloud policy for all 23 tools.

Get this rule live on your own Oracle Cloud server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY ORACLE CLOUD →

View all 23 tools →

These attack patterns abuse exactly the kind of access oci_adb_start gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so oci_adb_start only ever does what you allow.

SECURE ORACLE CLOUD →

Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the oci_adb_start tool do? +

Start a stopped Autonomous Database. It is categorised as a Execute tool in the Oracle Cloud MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on oci_adb_start? +

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

What risk level is oci_adb_start? +

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

Can I rate-limit oci_adb_start? +

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

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

oci_adb_start is provided by the Oracle Cloud MCP server (oracle-cloud-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Oracle Cloud tool call.

Deterministic rules across all 23 Oracle Cloud tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.