High Risk →

arcane_updater_run

Run the auto-updater to check and update all containers with available image updates

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

AI agents invoke arcane_updater_run to trigger processes or run actions in Arcane. 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.

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

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

See the full Arcane policy for all 180 tools.

Tool Name arcane_updater_run
Category Execute
MCP Server Arcane MCP Server
Risk Level High

View all 180 tools →

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

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

Run the auto-updater to check and update all containers with available image updates. It is categorised as a Execute tool in the Arcane MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on arcane_updater_run? +

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

What risk level is arcane_updater_run? +

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

Can I rate-limit arcane_updater_run? +

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

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

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

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

Currently onboarding teams running MCP in production.
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.

// REQUEST EARLY ACCESS

We're letting people in as fast as we can.

You're in the queue.

We'll be in touch as soon as we can let you in.