site_update · Voog MCP: Risk & Policy

WHAT IT DOES

What site_update does on Voog

AI agents use site_update to create or update resources in Voog — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Voog environment.

WHY IT NEEDS A POLICY

Why site_update needs a policy

This tool creates or modifies data reversibly at the site level (e.g., site name, domain settings, metadata). It is categorized as Write rather than Execute because it updates configuration data, not arbitrary operations. Severity is high due to the blast radius: misconfigured site-level settings could affect the entire CMS, user access, or site functionality, though effects remain reversible (can be updated again).

From the tool's definition Tool name 'site_update' explicitly indicates modification of site-level settings. Description states it updates 'site singleton' with 'root-level fields', confirming it modifies core site configuration attributes rather than deleting or executing code.

Risk signalsAdmin/system-level operation

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

site_update Rate-limited

site_update stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "site_update": {
      "limits": [
        {
          "counter": "site_update_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Voog, so you can run agents against it safely.

FAQ

Questions about site_update

What does the site_update tool do? +

Update site singleton. attributes: flat root-level fields. It is categorised as a Write tool in the Voog MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on site_update? +

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

What risk level is site_update? +

site_update is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit site_update? +

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

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

site_update is provided by the Voog MCP server (runnel/voog-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.