List AWX job templates (NOT for recent jobs or job history). Templates are playbook definitions, configurations, settings. This shows available templates to run, not execution history or recent activity. For recent jobs/runs/executions, use awx_jobs_list instead.
AI agents call awx_templates_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 and queries template definitions from AWX without creating, modifying, deleting, or executing anything. It is purely informational—listing available playbook configurations. The low severity reflects minimal blast radius; an agent listing templates cannot cause harm through this tool alone. Confidence is high due to explicit description and clear read-only semantics.
From the tool's definition Tool name 'awx_templates_list' and description explicitly states it 'List AWX job templates' and clarifies it shows 'available templates to run, not execution history or recent activity.' The verb 'list' is a read-only retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access awx_templates_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 awx_templates_list:
{
"version": "1",
"default": "deny",
"tools": {
"awx_templates_list": {}
}
}awx_templates_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 AWX job templates (NOT for recent jobs or job history). Templates are playbook definitions, configurations, settings. This shows available templates to run, not execution history or recent activity. For recent jobs/runs/executions, use awx_jobs_list instead. 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 awx_templates_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.
awx_templates_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 awx_templates_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 awx_templates_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.
awx_templates_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.