AI agents invoke lint_playbook to trigger actions in AAP Enterprise MCP Server. 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.
The name suggests running ansible-lint against a playbook, which executes a linting/analysis process. This is an Execute-category action as it runs an external tool. However, the description is empty, so confidence is reduced. Linting is generally read-only in effect but technically executes a process. Severity is medium given the server's access to AAP infrastructure, though linting itself has limited blast radius.
From the tool's definition Tool name 'lint_playbook' and server context mentioning 'ansible-lint'
Documented attack patterns abuse exactly the kind of access lint_playbook 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 lint_playbook:
{
"version": "1",
"default": "deny",
"tools": {
"lint_playbook": {
"limits": [
{
"counter": "lint_playbook_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}lint_playbook 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.
lint_playbook. It is categorised as a Execute tool in the AAP Enterprise MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the AAP Enterprise MCP Server MCP server in PolicyLayer and add a rule for lint_playbook: 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.
lint_playbook 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 lint_playbook 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 lint_playbook. 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.
lint_playbook 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.