Fetch a page from docs.ansible.com as clean Markdown.
AI agents call fetch_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.
This tool retrieves and queries publicly available documentation from docs.ansible.com, converting it to Markdown format. There are no modifications to data, code execution, deletions, or financial implications. The blast radius of misuse is minimal since it only accesses documentation resources that are already public.
From the tool's definition Tool name 'fetch_doc' and description 'Fetch a page from docs.ansible.com as clean Markdown' indicate a retrieval operation with no side effects. The verb 'fetch' and the action of reading documentation pages are characteristic of Read operations.
Attacks that exploit this kind of access
Fetch a page from docs.ansible.com as clean Markdown. 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 fetch_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.
fetch_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 fetch_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 fetch_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.
fetch_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 →