Update the name of an existing node in Tana. Note: This only works on plain text nodes - checkbox/boolean nodes cannot be renamed via the API.
AI agents use set_node_name to create or update resources in Tana MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tana MCP Server environment.
This tool modifies existing data (node names) in a Tana workspace but does not delete, destroy, or have irreversible effects. The change is reversible by updating the name again.
From the tool's definition Update the name of an existing node in Tana - tool explicitly updates/modifies existing data
Documented attack patterns abuse exactly the kind of access set_node_name gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Tana MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for set_node_name:
{
"version": "1",
"default": "deny",
"tools": {
"set_node_name": {
"limits": [
{
"counter": "set_node_name_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}set_node_name 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.
Free to start. No card required.
Update the name of an existing node in Tana. Note: This only works on plain text nodes - checkbox/boolean nodes cannot be renamed via the API. It is categorised as a Write tool in the Tana MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Tana MCP Server MCP server in PolicyLayer and add a rule for set_node_name: 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 Tana MCP Server. Nothing to install.
set_node_name is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the set_node_name 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.
Set action: deny in the PolicyLayer policy for set_node_name. 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.
set_node_name is provided by the Tana MCP Server MCP server (tim-mcdonnell/tana-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 12 Tana MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
12 Tana MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.