shell_list_allowed_commands

List the command prefixes that may be run without approval.

SERVERLocalAnt SOURCEyuga-hashimoto/localant

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/yuga-hashimoto-localant/shell-list-allowed-commands.md

WHAT IT DOES

What shell_list_allowed_commands does on LocalAnt

AI agents call shell_list_allowed_commands to retrieve information from LocalAnt without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why shell_list_allowed_commands is rated Low

This tool retrieves metadata about permitted shell commands through a simple listing operation. It has no side effects, does not execute commands, does not modify data, and does not create or delete resources.

From the tool's definition Tool name 'list_allowed_commands' and description 'List the command prefixes that may be run without approval' indicate a read-only query operation that retrieves configuration or policy information without modifying state or executing arbitrary commands.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

shell_list_allowed_commands Allowed

shell_list_allowed_commands is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "shell_list_allowed_commands": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about shell_list_allowed_commands

What does the shell_list_allowed_commands tool do? +

List the command prefixes that may be run without approval. It is categorised as a Read tool in the LocalAnt MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on shell_list_allowed_commands? +

Register the LocalAnt MCP server in PolicyLayer and add a rule for shell_list_allowed_commands: 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_list_allowed_commands? +

shell_list_allowed_commands is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit shell_list_allowed_commands? +

Yes. Add a rate_limit block to the shell_list_allowed_commands 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_list_allowed_commands completely? +

Set action: deny in the PolicyLayer policy for shell_list_allowed_commands. 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_list_allowed_commands? +

shell_list_allowed_commands 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

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →