update_page · Magnet MCP: Risk & Policy

WHAT IT DOES

What update_page does on Magnet

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

WHY IT NEEDS A POLICY

Why update_page needs a policy

The update_page tool modifies existing data (pages) reversibly through content updates. It does not delete or destroy data (would be Destructive), does not execute arbitrary code or external operations (would be Execute), and is not a read-only operation (would be Read).

From the tool's definition Tool description states 'Update an existing page in Magnet using markdown content. Only provided fields will be updated.' This is explicitly a modification operation on existing data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_page Rate-limited

update_page 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": {
    "update_page": {
      "limits": [
        {
          "counter": "update_page_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 Magnet, so you can run agents against it safely.

FAQ

Questions about update_page

What does the update_page tool do? +

Update an existing page in Magnet using markdown content. Only provided fields will be updated. Supports standard markdown syntax including headings, lists, code blocks, links, etc. It is categorised as a Write tool in the Magnet MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_page? +

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

What risk level is update_page? +

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

Can I rate-limit update_page? +

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

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

update_page is provided by the Magnet MCP server (@magnet-ai/magnet-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.