Lint a specific Ansible file and return issues.
AI agents call lint_file to retrieve information from AAP Enterprise MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Linting is a read-only static analysis operation that parses file content and returns diagnostic feedback. It has no side effects on infrastructure, data, or system state. The tool retrieves and analyzes information about an Ansible file but does not create, modify, execute, or delete any resources.
From the tool's definition Tool name 'lint_file' and description 'Lint a specific Ansible file and return issues' indicates static analysis that reviews and reports on file quality without modifying, executing, or deleting anything.
Documented attack patterns abuse exactly the kind of access lint_file 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_file:
{
"version": "1",
"default": "deny",
"tools": {
"lint_file": {}
}
}lint_file is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Lint a specific Ansible file and return issues. It is categorised as a Read tool in the AAP Enterprise MCP Server MCP Server, which means it retrieves data without modifying state.
Register the AAP Enterprise MCP Server MCP server in PolicyLayer and add a rule for lint_file: 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_file is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the lint_file 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_file. 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_file 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.