get_role_doc
AI agents call get_role_doc to retrieve information from Ansible Know without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears to retrieve Ansible role documentation based on naming conventions and the server's stated purpose of 'Module discovery, documentation search, and skill generation.' No description is provided, which slightly lowers confidence, but the pattern of sibling tools (fetch_doc, get_collection_docs, get_module_doc) all follow a retrieval/read pattern.
From the tool's definition Tool name 'get_role_doc' and server context indicating 'documentation search' and 'fetch_doc' as sibling tools suggest retrieval of documentation without side effects.
Attacks that exploit this kind of access
get_role_doc. It is categorised as a Read tool in the Ansible Know MCP Server, which means it retrieves data without modifying state.
Register the Ansible Know MCP server in PolicyLayer and add a rule for get_role_doc: 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 Know. Nothing to install.
get_role_doc 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_doc 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_doc. 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_doc is provided by the Ansible Know MCP server (leogallego/ansible-know-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →