New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

delete_action_secret

Delete a secret from an Action. Any template referencing ${NAME} will fail at invoke time with variable_missing until re-set.

SERVERDeloc SOURCEdelocdev/deloc-mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/deloc-mcp/delete-action-secret.md

What delete_action_secret does on Deloc

AI agents call delete_action_secret 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_secret is rated Critical

Deleting a secret is a destructive operation that cannot be undone. Once deleted, any Action templates depending on that secret will break at runtime. This ranks higher than Write (which is reversible) and falls clearly into Destructive.

From the tool's definition Tool name is 'delete_action_secret' and description states it will 'Delete a secret from an Action' causing templates referencing that secret to 'fail at invoke time' — this is irreversible deletion of stored configuration data.

Questions about delete_action_secret

What does the delete_action_secret tool do? +

Delete a secret from an Action. Any template referencing ${NAME} will fail at invoke time with variable_missing until re-set. 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.

How do I enforce a policy on delete_action_secret? +

Register the Deloc MCP server in PolicyLayer and add a rule for delete_action_secret: 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.

What risk level is delete_action_secret? +

delete_action_secret is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_action_secret? +

Yes. Add a rate_limit block to the delete_action_secret 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.

How do I block delete_action_secret completely? +

Set action: deny in the PolicyLayer policy for delete_action_secret. 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.

What MCP server provides delete_action_secret? +

delete_action_secret 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Deloc's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.