execute_dml · Oracle DB MCP Server MCP: Risk & Policy

WHAT IT DOES

What execute_dml does on Oracle DB MCP Server

AI agents use execute_dml to create or update resources in Oracle DB MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Oracle DB MCP Server environment.

WHY IT NEEDS A POLICY

Why execute_dml needs a policy

DML statements (INSERT, UPDATE, DELETE) modify data in the database. While DELETE is included, DML in Oracle is transactional and can be rolled back (unlike DDL), so it falls under Write rather than Destructive. However, severity is high because a misused DELETE or UPDATE without a WHERE clause could affect large volumes of data across the database, with significant blast radius.

From the tool's definition Execute a DML statement (INSERT, UPDATE, DELETE) on an Oracle database. Only works on connections with readwrite mode.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute_dml Rate-limited

execute_dml stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "execute_dml": {
      "limits": [
        {
          "counter": "execute_dml_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about execute_dml

What does the execute_dml tool do? +

Execute a DML statement (INSERT, UPDATE, DELETE) on an Oracle database. Only works on connections with readwrite mode. It is categorised as a Write tool in the Oracle DB MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on execute_dml? +

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

What risk level is execute_dml? +

execute_dml is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit execute_dml? +

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

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

execute_dml is provided by the Oracle DB MCP Server MCP server (titan213/oracle-db-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.