Delete chat message history for a specific flow.
AI agents call flowise_delete_chat_history to permanently remove resources in Flowise — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool permanently removes chat message history records. This is a destructive operation that cannot be undone. Although not as critical as deleting entire flows or financial data, the irreversible erasure of historical records poses a high severity risk if misused by an AI agent (e.g., covering audit trails or losing important conversation context). Destructive operations are more severe than Write operations.
From the tool's definition Tool name contains 'delete' and description states 'Delete chat message history' — irreversible removal of data.
Attacks that exploit this kind of access
Delete chat message history for a specific flow. It is categorised as a Destructive tool in the Flowise MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Flowise MCP server in PolicyLayer and add a rule for flowise_delete_chat_history: 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 Flowise. Nothing to install.
flowise_delete_chat_history 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 flowise_delete_chat_history 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 flowise_delete_chat_history. 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.
flowise_delete_chat_history is provided by the Flowise MCP server (julidir/flowise-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →