dry_run_ddl

A execute tool on the Mcpg MCP server.

SERVERMcpg SOURCEpypi:mcpg

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-devopam-mcpg/dry-run-ddl.md

WHAT IT DOES

What dry_run_ddl does on Mcpg

AI agents invoke dry_run_ddl to trigger actions in Mcpg. 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.

RISK

Why dry_run_ddl is rated High

DDL operations are executable statements that can modify database schema. A 'dry_run' variant suggests it validates or simulates DDL without permanent changes, but it still executes parsing and execution logic. The tool's impact depends on the DDL arguments provided (could range from Write for CREATE/ALTER to Destructive for DROP).

From the tool's definition Tool name 'dry_run_ddl' indicates execution of DDL (Data Definition Language) statements in a test mode. DDL encompasses CREATE, ALTER, DROP, and TRUNCATE operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs dry_run_ddl safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcpg, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For dry_run_ddl, this is the rule to start with:

dry_run_ddl Rate-limited

dry_run_ddl 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": {
    "dry_run_ddl": {
      "limits": [
        {
          "counter": "dry_run_ddl_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcpg, apply this rule, and every dry_run_ddl call is checked against it from then on.

FAQ

Questions about dry_run_ddl

What does the dry_run_ddl tool do? +

dry_run_ddl is a execute tool on the Mcpg MCP server. It is categorised as a Execute tool in the Mcpg MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on dry_run_ddl? +

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

What risk level is dry_run_ddl? +

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

Can I rate-limit dry_run_ddl? +

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

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

dry_run_ddl is provided by the Mcpg MCP server (pypi:mcpg). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcpg, and thousands of servers like it.

This server

All 252 Mcpg tools → High-risk tools on this server →

Across the catalogue

shortcuts_run on Apple Apps MCP →run_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →