get_collection_manifest
AI agents call get_collection_manifest 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 appears to retrieve manifest information about an Ansible collection—a read-only lookup operation consistent with other documentation and discovery functions on this server. No description is provided, which slightly lowers confidence, but the naming pattern and context strongly suggest it queries data without modification or execution of external effects.
From the tool's definition Tool name 'get_collection_manifest' suggests retrieving manifest data. Sibling tools like 'fetch_doc', 'get_module_doc', 'get_plugin_doc', and 'get_collection_docs' are all retrieval operations with no side effects.
Attacks that exploit this kind of access
get_collection_manifest. 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_collection_manifest: 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_collection_manifest 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_collection_manifest 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_collection_manifest. 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_collection_manifest 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 →