Remove a command prefix from the allowlist.
AI agents call shell_remove_allowed_command 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 removes entries from a security allowlist that controls which shell commands are permitted. Removing an allowlist entry is a destructive, security-relevant action — it could either re-restrict previously permitted operations or (depending on the system's default-allow/deny posture) open up previously blocked commands.
From the tool's definition Remove a command prefix from the allowlist
Attacks that exploit this kind of access
Remove a command prefix from the allowlist. 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 shell_remove_allowed_command: 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.
shell_remove_allowed_command 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 shell_remove_allowed_command 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 shell_remove_allowed_command. 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.
shell_remove_allowed_command 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 →