AI agents call coding_agent_list to retrieve information from LocalAnt without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and reports information about configured coding agents and their availability status. It performs a passive read operation without modifying, executing, or deleting anything. The deprecation status does not change its classification. The low severity reflects that exposure only reveals local system configuration details without enabling actions or data modification.
From the tool's definition Tool name is 'coding_agent_list' and description states 'List configured coding agents and whether their CLI is available.' The verb 'list' and the purpose of retrieving status information indicate a query operation with no side effects.
Attacks that exploit this kind of access
${DEPRECATED} List configured coding agents and whether their CLI is available. It is categorised as a Read tool in the LocalAnt MCP Server, which means it retrieves data without modifying state.
Register the LocalAnt MCP server in PolicyLayer and add a rule for coding_agent_list: 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.
coding_agent_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the coding_agent_list 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 coding_agent_list. 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.
coding_agent_list 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 →