Create host in AWX inventory
AI agents use awx_inventory_host_create to create or update resources in Pypi:awx — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pypi:awx environment.
This tool creates a new host entry in an AWX (Ansible Tower) inventory, which is a reversible write operation. While not destructive, it modifies the infrastructure configuration. Severity is high because unauthorized host creation in an Ansible/AWX system could lead to unauthorized command execution, lateral movement, or infrastructure compromise if a malicious actor adds hosts under their control to the inventory.
From the tool's definition Tool name contains 'create' and description states 'Create host in AWX inventory' — this adds a new resource to an infrastructure management system.
Documented attack patterns abuse exactly the kind of access awx_inventory_host_create 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_inventory_host_create:
{
"version": "1",
"default": "deny",
"tools": {
"awx_inventory_host_create": {
"limits": [
{
"counter": "awx_inventory_host_create_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}awx_inventory_host_create 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.
Free to start. No card required.
Create host in AWX inventory. It is categorised as a Write tool in the Pypi:awx MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Pypi:awx MCP server in PolicyLayer and add a rule for awx_inventory_host_create: 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_inventory_host_create is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the awx_inventory_host_create 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_inventory_host_create. 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_inventory_host_create 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.