Remove a stored secret by name (risk 4).
AI agents call secret_remove to permanently remove resources in LocalAnt — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes stored secrets, which cannot be undone. While not as broadly destructive as deleting entire databases, removing authentication credentials creates unrecoverable data loss and could break dependent systems. This is a classic Destructive action.
From the tool's definition Tool name is 'secret_remove' with description 'Remove a stored secret by name'. The verb 'remove' combined with 'secret' indicates irreversible deletion of sensitive stored credentials or tokens.
Attacks that exploit this kind of access
Remove a stored secret by name (risk 4). It is categorised as a Destructive tool in the LocalAnt MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the LocalAnt MCP server in PolicyLayer and add a rule for secret_remove: 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 LocalAnt. Nothing to install.
secret_remove 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 secret_remove 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 secret_remove. 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.
secret_remove is provided by the LocalAnt MCP server (yuga-hashimoto/localant). 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 →