Installs or lists Ansible collections and roles from Galaxy or a requirements file.
AI agents invoke ansible-galaxy to trigger actions in Lint. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Installing Ansible collections/roles from Galaxy fetches external packages and writes them to the filesystem, which is an external operation with side effects beyond simple data retrieval. While it can also 'list' (a read operation), the install capability makes Execute the most severe applicable category. Misuse could install malicious collections or overwrite existing ones.
From the tool's definition 'Installs or lists Ansible collections and roles from Galaxy or a requirements file' — the install operation downloads and places files on the filesystem, triggering external network operations and modifying the environment.
Documented attack patterns abuse exactly the kind of access ansible-galaxy gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Lint, and nothing reaches the server without passing your rules. This is the rule we recommend for ansible-galaxy:
{
"version": "1",
"default": "deny",
"tools": {
"ansible-galaxy": {
"limits": [
{
"counter": "ansible-galaxy_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}ansible-galaxy stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Installs or lists Ansible collections and roles from Galaxy or a requirements file. It is categorised as a Execute tool in the Lint MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Lint MCP server in PolicyLayer and add a rule for ansible-galaxy: 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 Lint. Nothing to install.
ansible-galaxy is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the ansible-galaxy 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 ansible-galaxy. 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.
ansible-galaxy is provided by the Lint MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Lint, 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.
202 Lint tools catalogued and risk-classified — across an index of 43,000+ MCP servers.