secret_remove

Remove a stored secret by name (risk 4).

SERVERLocalAnt SOURCEyuga-hashimoto/localant

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/yuga-hashimoto-localant/secret-remove.md

WHAT IT DOES

What secret_remove does on LocalAnt

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.

RISK

Why secret_remove is rated Critical

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

RECOMMENDED RULE

The rule that runs secret_remove safely

PolicyLayer is an MCP gateway: it sits between your AI agents and LocalAnt, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For secret_remove, this is the rule to start with:

secret_remove Hidden

secret_remove is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "secret_remove"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect LocalAnt, apply this rule, and every secret_remove call is checked against it from then on.

FAQ

Questions about secret_remove

What does the secret_remove tool do? +

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.

How do I enforce a policy on secret_remove? +

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.

What risk level is secret_remove? +

secret_remove 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 secret_remove? +

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.

How do I block secret_remove completely? +

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.

What MCP server provides secret_remove? +

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.

KEEP EXPLORING

More on LocalAnt, and thousands of servers like it.

This server

All 216 LocalAnt tools → Critical-risk tools on this server →

Across the catalogue

remove_video on Mcptube Vision →remove_2fa on cPanel MCP Server →remove_concept on MegaMemory →task_assignees_remove on Vikunja → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →