history_goto · SVG Canvas MCP: Risk & Policy

WHAT IT DOES

What history_goto does on SVG Canvas MCP

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

WHY IT NEEDS A POLICY

Why history_goto needs a policy

This tool navigates to a specific history state, which modifies the current canvas state (similar to undo/redo). It is reversible since history navigation can go forward and back, placing it in Write rather than Destructive. The blast radius is medium as it could overwrite current unsaved work on the SVG canvas.

From the tool's definition '히스토리의 특정 시점으로 이동합니다' — navigates to a specific point in history, effectively restoring/modifying canvas state

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

history_goto Rate-limited

history_goto 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": {
    "history_goto": {
      "limits": [
        {
          "counter": "history_goto_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 SVG Canvas MCP, so you can run agents against it safely.

FAQ

Questions about history_goto

What does the history_goto tool do? +

히스토리의 특정 시점으로 이동합니다. It is categorised as a Write tool in the SVG Canvas MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on history_goto? +

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

What risk level is history_goto? +

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

Can I rate-limit history_goto? +

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

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

history_goto is provided by the SVG Canvas MCP server (kim62210/svg-canvas-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.