Get detailed information about a specific Ansible Galaxy role.
AI agents call get_role_details 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.
This tool retrieves metadata and details about Ansible Galaxy roles, which is a read-only query operation with no side effects. It does not create, modify, delete, or execute any resources. The blast radius of misuse is minimal—an agent could retrieve unwanted information but cannot harm systems or data.
From the tool's definition Tool name 'get_role_details' and description 'Get detailed information about a specific Ansible Galaxy role' indicate retrieval of data without modification, deletion, or execution of code.
Documented attack patterns abuse exactly the kind of access get_role_details 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 get_role_details:
{
"version": "1",
"default": "deny",
"tools": {
"get_role_details": {}
}
}get_role_details 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.
Get detailed information about a specific Ansible Galaxy role. 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 get_role_details: 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.
get_role_details 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 get_role_details 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 get_role_details. 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.
get_role_details 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.