dry_run_workflow

Dry-run a workflow draft through the control plane. If the API is unavailable, returns a local policy/audit execution plan for review.

SERVERAdrata SOURCE@adrata/adrata-mcp

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/adrata-adrata-mcp/dry-run-workflow.md

WHAT IT DOES

What dry_run_workflow does on Adrata

AI agents invoke dry_run_workflow to trigger actions in Adrata. 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_workflow is rated High

dry_run_workflow triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs dry_run_workflow safely

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

dry_run_workflow Rate-limited

dry_run_workflow 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_workflow": {
      "limits": [
        {
          "counter": "dry_run_workflow_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 Adrata, apply this rule, and every dry_run_workflow call is checked against it from then on.

FAQ

Questions about dry_run_workflow

What does the dry_run_workflow tool do? +

Dry-run a workflow draft through the control plane. If the API is unavailable, returns a local policy/audit execution plan for review. It is categorised as a Execute tool in the Adrata 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_workflow? +

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

What risk level is dry_run_workflow? +

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

Can I rate-limit dry_run_workflow? +

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

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

dry_run_workflow is provided by the Adrata MCP server (@adrata/adrata-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Adrata, and thousands of servers like it.

This server

All 278 Adrata tools → High-risk tools on this server →

Across the catalogue

run on 0sec →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 →