Execute write operations (UPDATE, DELETE, INSERT, etc.) when enable_updates=true
AI agents call execute to permanently remove resources in Treasure Data MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool explicitly executes write operations including DELETE, which is irreversible. It also supports UPDATE and INSERT which are destructive/write in nature. Since the most severe applicable category is Destructive (due to DELETE capability), and this tool can operate on a data platform at scale, the blast radius is critical — a misused DELETE or UPDATE could wipe or corrupt large datasets irreversibly.
From the tool's definition Execute write operations (UPDATE, DELETE, INSERT, etc.) when enable_updates=true
Documented attack patterns abuse exactly the kind of access execute gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Treasure Data MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for execute:
{
"version": "1",
"default": "deny",
"hide": [
"execute"
]
}execute 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.
Execute write operations (UPDATE, DELETE, INSERT, etc.) when enable_updates=true. It is categorised as a Destructive tool in the Treasure Data MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Treasure Data MCP Server MCP server in PolicyLayer and add a rule for execute: 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 Treasure Data MCP Server. Nothing to install.
execute 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 execute 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 execute. 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.
execute is provided by the Treasure Data MCP Server MCP server (treasure-data/td-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Treasure Data MCP Server, 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.
23 Treasure Data MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.