High Risk →

bighub_actions_dry_run

Dry-run action evaluation (non-persistent) via /actions/evaluate with dry_run=true.

Accepts raw HTML/template content (payload)

Part of the BIGHUB MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

@bighub/bighub-mcp Execute Risk 3/5

AI agents invoke bighub_actions_dry_run to trigger processes or run actions in BIGHUB. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

bighub_actions_dry_run can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

bighub.yaml
tools:
  bighub_actions_dry_run:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full BIGHUB policy for all 125 tools.

Tool Name bighub_actions_dry_run
Category Execute
MCP Server BIGHUB MCP Server
Risk Level High

View all 125 tools →

Agents calling execute-class tools like bighub_actions_dry_run have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

bighub_actions_dry_run is one of the high-risk operations in BIGHUB. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.

What does the bighub_actions_dry_run tool do? +

Dry-run action evaluation (non-persistent) via /actions/evaluate with dry_run=true.. It is categorised as a Execute tool in the BIGHUB MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on bighub_actions_dry_run? +

Add a rule in your Intercept YAML policy under the tools section for bighub_actions_dry_run. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the BIGHUB MCP server.

What risk level is bighub_actions_dry_run? +

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

Can I rate-limit bighub_actions_dry_run? +

Yes. Add a rate_limit block to the bighub_actions_dry_run rule in your Intercept 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 bighub_actions_dry_run completely? +

Set action: deny in the Intercept policy for bighub_actions_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 bighub_actions_dry_run? +

bighub_actions_dry_run is provided by the BIGHUB MCP server (@bighub/bighub-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on BIGHUB

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.