Add an external server to the Ansible inventory
AI agents use add-external-server to create or update resources in Ansible — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ansible environment.
This tool creates or modifies Ansible inventory entries by adding a new external server. This is a Write operation—it mutates configuration data but is reversible (servers can be removed or modified later). It does not delete data (ruling out Destructive), execute arbitrary code on targets (ruling out Execute), move money (ruling out Financial), or retrieve information (ruling out Read).
From the tool's definition Tool name: 'add-external-server'; Description: 'Add an external server to the Ansible inventory'. The verb 'Add' indicates creation/modification of inventory data, which is reversible.
Documented attack patterns abuse exactly the kind of access add-external-server gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Ansible, and nothing reaches the server without passing your rules. This is the rule we recommend for add-external-server:
{
"version": "1",
"default": "deny",
"tools": {
"add-external-server": {
"limits": [
{
"counter": "add-external-server_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add-external-server 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.
Add an external server to the Ansible inventory. It is categorised as a Write tool in the Ansible MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ansible MCP server in PolicyLayer and add a rule for add-external-server: 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 Ansible. Nothing to install.
add-external-server 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 add-external-server 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 add-external-server. 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.
add-external-server is provided by the Ansible MCP server (washyu/ansible-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Ansible, 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.
90 Ansible tools catalogued and risk-classified — across an index of 43,000+ MCP servers.