Delete an Infisical project.
AI agents call delete_project 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 performs an irreversible destructive action—deleting an entire project. This is categorized as Destructive rather than Write because deletion cannot be reversed. The severity is high because a misused delete_project call would permanently remove a project and all associated data (environments, secrets, identities, roles, etc.), causing significant operational disruption.
From the tool's definition Tool name 'delete_project' combined with description 'Delete an Infisical project' explicitly indicates irreversible deletion of a project resource. Deletion operations cannot be undone and result in permanent data loss.
Attacks that exploit this kind of access
Delete an Infisical project. 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_project: 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_project 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_project 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_project. 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_project 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 →