automation_dry_run

Read current observations and say what would fire now without actions or state changes.

SERVERTolpo SOURCEsignerless/tolpo

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/tolpo/automation-dry-run.md

WHAT IT DOES

What automation_dry_run does on Tolpo

AI agents invoke automation_dry_run to trigger actions in Tolpo. 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 automation_dry_run is rated High

automation_dry_run 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 automation_dry_run safely

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

automation_dry_run Rate-limited

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

FAQ

Questions about automation_dry_run

What does the automation_dry_run tool do? +

Read current observations and say what would fire now without actions or state changes. It is categorised as a Execute tool in the Tolpo MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on automation_dry_run? +

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

What risk level is automation_dry_run? +

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

Can I rate-limit automation_dry_run? +

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

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

automation_dry_run is provided by the Tolpo MCP server (signerless/tolpo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Tolpo, and thousands of servers like it.

This server

All 243 Tolpo tools → High-risk tools on this server →

Across the catalogue

editor_run_template on 010 Editor →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 →