Delete records from datasets using advanced filters
AI agents call delete_data to permanently remove resources in OrgFlow MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes data without an undo mechanism. The use of 'delete' combined with 'records from datasets' indicates destructive action. While not financial in nature, the high blast radius of accidental or malicious record deletion in an organizational context (employee data, project records, asset information) justifies 'high' severity.
From the tool's definition Tool name 'delete_data' and description 'Delete records from datasets using advanced filters' explicitly performs irreversible deletion of data records.
Attacks that exploit this kind of access
Delete records from datasets using advanced filters. It is categorised as a Destructive tool in the OrgFlow MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the OrgFlow MCP server in PolicyLayer and add a rule for delete_data: 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 OrgFlow MCP. Nothing to install.
delete_data 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 delete_data 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 delete_data. 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.
delete_data is provided by the OrgFlow MCP server (sujalpat1810/orgflow_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 →