update_template_doc · ComfyUI-APP- MCP: Risk & Policy

WHAT IT DOES

What update_template_doc does on ComfyUI-APP-MCP

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

WHY IT NEEDS A POLICY

Why update_template_doc needs a policy

The name pattern (update_*) and context within a template management system indicates this is a Write operation—it modifies data reversibly. Documentation updates can be undone or corrected, distinguishing it from Destructive operations. However, confidence is moderate (0.75) due to the empty description, which prevents definitive confirmation of scope and potential side effects.

From the tool's definition Tool name 'update_template_doc' indicates modification of template documentation. The sibling tools include 'read_template_doc' and 'run_template', suggesting this tool creates or modifies reversible documentation records within the ComfyUI workflow system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_template_doc Rate-limited

update_template_doc 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_template_doc": {
      "limits": [
        {
          "counter": "update_template_doc_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 ComfyUI-APP-MCP, so you can run agents against it safely.

FAQ

Questions about update_template_doc

What does the update_template_doc tool do? +

update_template_doc. It is categorised as a Write tool in the ComfyUI-APP-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 update_template_doc? +

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

What risk level is update_template_doc? +

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

Can I rate-limit update_template_doc? +

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

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

update_template_doc is provided by the ComfyUI-APP- MCP server (luo-lotus/comfyui-app-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.