AI agents call env_list to retrieve information from Pypi:awx without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves configuration data about AWX environments without side effects. It is a simple list operation that gathers information, making it a Read category tool. The severity is low because listing environments does not expose sensitive credentials directly (though AWX environment names might hint at infrastructure) and has no direct blast radius for misuse by an AI agent.
From the tool's definition Tool name 'env_list' and description 'List all configured AWX environments' indicate a query/retrieval operation with no modification or execution of commands.
Documented attack patterns abuse exactly the kind of access env_list gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Pypi:awx, and nothing reaches the server without passing your rules. This is the rule we recommend for env_list:
{
"version": "1",
"default": "deny",
"tools": {
"env_list": {}
}
}env_list is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all configured AWX environments. It is categorised as a Read tool in the Pypi:awx MCP Server, which means it retrieves data without modifying state.
Register the Pypi:awx MCP server in PolicyLayer and add a rule for env_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 Pypi:awx. Nothing to install.
env_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 env_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 env_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.
env_list is provided by the Pypi:awx MCP server (SurgeX-Labs/awx-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Pypi:awx, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
50 Pypi:awx tools catalogued and risk-classified — across an index of 43,000+ MCP servers.