execute_dml · Springboot Test MCP: Risk & Policy

WHAT IT DOES

What execute_dml does on Springboot Test

AI agents invoke execute_dml to trigger actions in Springboot Test. 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_dml needs a policy

While DML operations (INSERT/UPDATE/DELETE) are reversible and thus not Destructive in the strict sense, they are Execute-category tools because they modify data irreversibly within a transaction context and their effects depend on the specific DML arguments provided.

From the tool's definition Tool executes DML statements (INSERT/UPDATE/DELETE) on Oracle database. The description explicitly names these data modification operations, which are executable statements with side effects.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute_dml Rate-limited

execute_dml 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_dml": {
      "limits": [
        {
          "counter": "execute_dml_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 Springboot Test, 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 Oracle database. It is categorised as a Execute tool in the Springboot Test 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_dml? +

Register the Springboot Test 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 Springboot Test. Nothing to install.

What risk level is execute_dml? +

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

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 Springboot Test MCP server (kenlin-7/springboot-test-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.