execute_plsql · Oracle DB MCP Server MCP: Risk & Policy

WHAT IT DOES

What execute_plsql does on Oracle DB MCP Server

AI agents invoke execute_plsql to trigger actions in Oracle DB 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 execute_plsql needs a policy

This tool permits execution of arbitrary PL/SQL code and DDL statements, which can create functions, procedures, and modify database schema. While it doesn't inherently delete data (which would be Destructive), it can execute complex operations with side effects that cannot always be predicted or reversed without additional operations.

From the tool's definition Tool description states it "Execute[s] a PL/SQL block or DDL statement (CREATE FUNCTION, CREATE PROCEDURE, etc.)" which allows running arbitrary code blocks and data definition statements that trigger external operations and schema modifications whose effects…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute_plsql Rate-limited

execute_plsql 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": {
    "execute_plsql": {
      "limits": [
        {
          "counter": "execute_plsql_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 Oracle DB MCP Server, so you can run agents against it safely.

FAQ

Questions about execute_plsql

What does the execute_plsql tool do? +

Execute a PL/SQL block or DDL statement (CREATE FUNCTION, CREATE PROCEDURE, etc.). Only works on connections with readwrite mode. It is categorised as a Execute tool in the Oracle DB 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 execute_plsql? +

Register the Oracle DB MCP Server MCP server in PolicyLayer and add a rule for execute_plsql: 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_plsql? +

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

Can I rate-limit execute_plsql? +

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

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

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