Manage n8n data tables and rows. Actions: createTable, listTables, getTable, updateTable, deleteTable, getRows, insertRows, updateRows, upsertRows, deleteRows.
AI agents call n8n_manage_datatable to permanently remove resources in N8n — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool supports deleteTable and deleteRows which are irreversible destructive operations. Per the rules, when a tool spans categories, the most severe applies — Destructive > Execute > Write > Read. Misuse by an AI agent could permanently destroy entire data tables and their contents, warranting critical severity.
From the tool's definition Actions include: deleteTable, deleteRows — irreversible deletion of entire tables or rows; also includes createTable, updateTable, insertRows, updateRows, upsertRows covering the full data lifecycle
Documented attack patterns abuse exactly the kind of access n8n_manage_datatable gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and N8n, and nothing reaches the server without passing your rules. This is the rule we recommend for n8n_manage_datatable:
{
"version": "1",
"default": "deny",
"hide": [
"n8n_manage_datatable"
]
} n8n_manage_datatable disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Manage n8n data tables and rows. Actions: createTable, listTables, getTable, updateTable, deleteTable, getRows, insertRows, updateRows, upsertRows, deleteRows. It is categorised as a Destructive tool in the N8n MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the N8n MCP server in PolicyLayer and add a rule for n8n_manage_datatable: 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 N8n. Nothing to install.
n8n_manage_datatable is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the n8n_manage_datatable 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 n8n_manage_datatable. 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.
n8n_manage_datatable is provided by the N8n MCP server (@czlonkowski/n8n-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from N8n, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
22 N8n tools catalogued and risk-classified — across an index of 43,000+ MCP servers.