shell_add_allowed_command

Add a command prefix to the allowlist.

SERVERLocalAnt SOURCEyuga-hashimoto/localant

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/yuga-hashimoto-localant/shell-add-allowed-command.md

WHAT IT DOES

What shell_add_allowed_command does on LocalAnt

AI agents use shell_add_allowed_command to create or update resources in LocalAnt, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your LocalAnt environment.

RISK

Why shell_add_allowed_command is rated Medium

This tool modifies the security allowlist that controls which shell commands can be executed. While it is a Write operation (creating/modifying a configuration entry), its blast radius is high because adding a command prefix to the allowlist could enable subsequent execution of previously blocked shell commands, effectively expanding the attack surface.

From the tool's definition Add a command prefix to the allowlist

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs shell_add_allowed_command 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 shell_add_allowed_command, this is the rule to start with:

shell_add_allowed_command Rate-limited

shell_add_allowed_command stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "shell_add_allowed_command": {
      "limits": [
        {
          "counter": "shell_add_allowed_command_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about shell_add_allowed_command

What does the shell_add_allowed_command tool do? +

Add a command prefix to the allowlist. It is categorised as a Write tool in the LocalAnt MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on shell_add_allowed_command? +

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

What risk level is shell_add_allowed_command? +

shell_add_allowed_command is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit shell_add_allowed_command? +

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

How do I block shell_add_allowed_command completely? +

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

What MCP server provides shell_add_allowed_command? +

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

KEEP EXPLORING

More on LocalAnt, and thousands of servers like it.

This server

All 216 LocalAnt tools →

Across the catalogue

add-tag on Kanban MCP Server →kb_add on Persistent Kb → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →