add_template_transform_node · Dify MCP: Risk & Policy

WHAT IT DOES

What add_template_transform_node does on Dify MCP

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

WHY IT NEEDS A POLICY

Why add_template_transform_node needs a policy

The tool adds a node to a Dify workflow, which is a reversible modification of workflow structure. This aligns with the Write category (creates or modifies data reversibly). Severity is medium because misuse could create malformed or unintended workflow logic, but the impact is limited to workflow definition structure within Dify and can be undone.

From the tool's definition Tool name 'add_template_transform_node' indicates creation/modification of workflow nodes. Sibling tools like 'add_answer_node', 'add_edge', 'add_llm_node', 'add_start_node', and 'create_workflow' all perform Write operations (creating/modifying workflow…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_template_transform_node Rate-limited

add_template_transform_node 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": {
    "add_template_transform_node": {
      "limits": [
        {
          "counter": "add_template_transform_node_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 Dify MCP, so you can run agents against it safely.

FAQ

Questions about add_template_transform_node

What does the add_template_transform_node tool do? +

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

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

What risk level is add_template_transform_node? +

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

Can I rate-limit add_template_transform_node? +

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

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

add_template_transform_node is provided by the Dify MCP server (taiki-kuraishi/dify-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.