Handle user decision for duplicate service
AI agents use handle-duplicate-service 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.
The tool modifies infrastructure state by acting on user decisions regarding duplicate services. This is a reversible write operation—it updates or reconciles service configurations rather than permanently deleting them or executing arbitrary operations. The medium severity reflects that misuse could corrupt service configurations, but the operation is not destructive (reversible) or financial.
From the tool's definition Tool name 'handle-duplicate-service' and description 'Handle user decision for duplicate service' indicate modification of service state based on user input.
Documented attack patterns abuse exactly the kind of access handle-duplicate-service 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 handle-duplicate-service:
{
"version": "1",
"default": "deny",
"tools": {
"handle-duplicate-service": {
"limits": [
{
"counter": "handle-duplicate-service_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}handle-duplicate-service 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.
Handle user decision for duplicate service. 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 handle-duplicate-service: 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.
handle-duplicate-service 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 handle-duplicate-service 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 handle-duplicate-service. 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.
handle-duplicate-service 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.