High Risk →

run_dogfood_surge

Executes the standardized dogfooding sequence: sets baseline, triggers a 30k fish surge, and returns status.

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

glazyr/glazyr-viz Execute Risk 3/5

AI agents invoke run_dogfood_surge to trigger processes or run actions in Glazyr Viz. 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.

run_dogfood_surge 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.

glazyr-glazyr-viz.yaml
tools:
  run_dogfood_surge:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full Glazyr Viz policy for all 10 tools.

Tool Name run_dogfood_surge
Category Execute
Risk Level High

View all 10 tools →

Agents calling execute-class tools like run_dogfood_surge 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.

run_dogfood_surge is one of the high-risk operations in Glazyr Viz. 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 run_dogfood_surge tool do? +

Executes the standardized dogfooding sequence: sets baseline, triggers a 30k fish surge, and returns status.. It is categorised as a Execute tool in the Glazyr Viz MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_dogfood_surge? +

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

What risk level is run_dogfood_surge? +

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

Can I rate-limit run_dogfood_surge? +

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

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

run_dogfood_surge is provided by the Glazyr Viz MCP server (glazyr/glazyr-viz). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Glazyr Viz

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.