AI agents use create_file_node 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 creates new data (a file attachment node) in a reversible manner. File attachments can typically be deleted or replaced, making this a Write operation rather than Destructive. The severity is medium because while it modifies workspace data, the impact is localized to a single file node attachment and doesn't affect critical system operations or financial data.
From the tool's definition Tool name 'create_file_node' and description 'Create a file attachment node in Tana' indicate creation of new data (file attachment) within the Tana workspace.
Documented attack patterns abuse exactly the kind of access create_file_node 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 create_file_node:
{
"version": "1",
"default": "deny",
"tools": {
"create_file_node": {
"limits": [
{
"counter": "create_file_node_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_file_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.
Free to start. No card required.
Create a file attachment node in Tana. 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 create_file_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 Tana MCP Server. Nothing to install.
create_file_node 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 create_file_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.
Set action: deny in the PolicyLayer policy for create_file_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.
create_file_node 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.