Soft-delete an AI tool by name. The row is retained so in-flight runs that already loaded the tool can finish, but it is hidden from all user-facing queries and the executor stops loading it for new runs (is_active=False is set alongside). History is preserved. Calling flowforge_create_tool with ...
Part of the Flowforge server.
Free to start. No card required.
AI agents may call flowforge_delete_tool to permanently remove or destroy resources in Flowforge. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.
Without a policy, an AI agent could call flowforge_delete_tool in a loop, permanently destroying resources in Flowforge. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.
Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.
{
"version": "1",
"default": "deny",
"hide": [
"flowforge_delete_tool"
]
}See the full Flowforge policy for all 49 tools.
These attack patterns abuse exactly the kind of access flowforge_delete_tool gives an agent. Each links to the full case and the policy that stops it:
Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.
Soft-delete an AI tool by name. The row is retained so in-flight runs that already loaded the tool can finish, but it is hidden from all user-facing queries and the executor stops loading it for new runs (is_active=False is set alongside). History is preserved. Calling flowforge_create_tool with the same name restores the row. Built-in tools cannot be deleted.. It is categorised as a Destructive tool in the Flowforge MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Flowforge MCP server in PolicyLayer and add a rule for flowforge_delete_tool: 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 Flowforge. Nothing to install.
flowforge_delete_tool 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 flowforge_delete_tool 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 flowforge_delete_tool. 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.
flowforge_delete_tool is provided by the Flowforge MCP server (flowforge-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 49 Flowforge tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.