Search a library's official documentation for specific questions or keywords.
AI agents call get_library_docs to retrieve information from OmniDocs MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves documentation content. It has no side effects, does not create, modify, delete, or execute anything. The severity is low because misuse (e.g., searching for misleading documentation excerpts) poses minimal operational risk compared to write, execute, or destructive actions.
From the tool's definition Tool description states it 'Search[es] a library's official documentation' — a retrieval operation. The server's purpose is to 'crawl, index, and semantically search official framework documentation' without modifying or executing code.
Attacks that exploit this kind of access
Search a library's official documentation for specific questions or keywords. It is categorised as a Read tool in the OmniDocs MCP MCP Server, which means it retrieves data without modifying state.
Register the OmniDocs MCP server in PolicyLayer and add a rule for get_library_docs: 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 OmniDocs MCP. Nothing to install.
get_library_docs 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_library_docs 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_library_docs. 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_library_docs is provided by the OmniDocs MCP server (yogesh-g-3468/omnidocs-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 →