Delete a deployed function from a project.
AI agents call delete_function to permanently remove resources in Run402 — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion of a deployed function is an irreversible action that destroys production code and cannot be undone without restoration from backups. This is a destructive operation. Severity is high because the blast radius depends on which function is deleted (could be critical infrastructure), but the action itself is permanent and disruptive to the deployed system.
From the tool's definition Tool name is 'delete_function' and description states 'Delete a deployed function from a project' — the verb 'Delete' indicates irreversible removal of deployed code.
Attacks that exploit this kind of access
Delete a deployed function from a project. It is categorised as a Destructive tool in the Run402 MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Run402 MCP server in PolicyLayer and add a rule for delete_function: 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 Run402. Nothing to install.
delete_function 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_function 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_function. 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_function is provided by the Run402 MCP server (kychee-com/run402). 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 →