AI agents use enable_activation to create or update resources in AAP Enterprise MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AAP Enterprise MCP Server environment.
This tool creates or modifies data reversibly by changing the enabled state of an activation. It is a Write operation because it alters configuration state without permanently deleting data and can be undone by calling a corresponding disable function.
From the tool's definition Tool name is 'enable_activation' and description states 'Enable an activation.' The verb 'enable' indicates a state change operation that modifies an existing activation resource in Red Hat's Ansible Automation Platform.
Documented attack patterns abuse exactly the kind of access enable_activation gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and AAP Enterprise MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for enable_activation:
{
"version": "1",
"default": "deny",
"tools": {
"enable_activation": {
"limits": [
{
"counter": "enable_activation_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}enable_activation 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.
Enable an activation. It is categorised as a Write tool in the AAP Enterprise MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the AAP Enterprise MCP Server MCP server in PolicyLayer and add a rule for enable_activation: 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 AAP Enterprise MCP Server. Nothing to install.
enable_activation 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 enable_activation 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 enable_activation. 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.
enable_activation is provided by the AAP Enterprise MCP Server MCP server (sibilleb/aap-enterprise-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 69 AAP Enterprise MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
69 AAP Enterprise MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.