page_update · Voog MCP: Risk & Policy

WHAT IT DOES

What page_update does on Voog

AI agents use page_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 page_update needs a policy

This tool creates or modifies data reversibly (fits Write category). It updates pages in a CMS, which is a standard content modification operation. Severity is high because arbitrary field updates on pages in a CMS can affect site structure, layout, content, and metadata across potentially many visitors, though changes are reversible (not Destructive).

From the tool's definition Tool name 'page_update' and description phrase 'Update arbitrary fields on a page' directly indicate modification of existing data. The word 'arbitrary' suggests broad write capabilities across page properties.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

page_update Rate-limited

page_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": {
    "page_update": {
      "limits": [
        {
          "counter": "page_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 page_update

What does the page_update tool do? +

Update arbitrary fields on a page. At least one of. 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 page_update? +

Register the Voog MCP server in PolicyLayer and add a rule for page_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 page_update? +

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

Can I rate-limit page_update? +

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

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

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