Delete an Infisical folder by ID or name.
AI agents call delete_folder to permanently remove resources in Infisical MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes a folder from Infisical, which cannot be undone. Deletion is irreversible data destruction, making it Destructive rather than Write. The blast radius is high because an AI agent with this tool could delete entire folder structures containing secrets and configurations, potentially disrupting critical infrastructure or exposing security lapses.
From the tool's definition Tool name is 'delete_folder' and description states 'Delete an Infisical folder by ID or name.' The use of 'Delete' indicates irreversible removal of data.
Attacks that exploit this kind of access
Delete an Infisical folder by ID or name. It is categorised as a Destructive tool in the Infisical MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Infisical MCP server in PolicyLayer and add a rule for delete_folder: 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 Infisical MCP. Nothing to install.
delete_folder 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_folder 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_folder. 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_folder is provided by the Infisical MCP server (plgonzalezrx8/infisicalmcp). 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 →