delete_action
Permanently delete an Action. All secrets and invocation logs are cascaded. Irreversible.
This record as markdown: /tools/deloc-mcp/delete-action.md
What delete_action does on Deloc
AI agents call delete_action to permanently remove resources in Deloc, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_action is rated Critical
This tool permanently removes an Action and its associated secrets and logs without the ability to undo the operation. This is irreversible data destruction, making it Destructive rather than merely Write.
From the tool's definition Tool description explicitly states 'Permanently delete an Action' with 'All secrets and invocation logs are cascaded. Irreversible.' The keywords 'Permanently delete' and 'Irreversible' directly indicate destructive, non-recoverable data loss.
Attacks that exploit this kind of access
The rule that runs delete_action safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Deloc, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_action, this is the rule to start with:
delete_action is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Deloc, apply this rule, and every delete_action call is checked against it from then on.
Questions about delete_action
Permanently delete an Action. All secrets and invocation logs are cascaded. Irreversible. It is categorised as a Destructive tool in the Deloc MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Deloc MCP server in PolicyLayer and add a rule for delete_action: 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 Deloc. Nothing to install.
delete_action 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_action 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_action. 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_action is provided by the Deloc MCP server (delocdev/deloc-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Deloc, and thousands of servers like it.
Across the catalogue