Point to a package.json or requirements.txt file to auto-discover libraries,
AI agents call auto_import_from_manifest 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.
The tool reads a dependency manifest file (package.json or requirements.txt) to auto-discover libraries for indexing. This is primarily a Read/discovery action, though it may trigger subsequent indexing/write operations internally. The description is somewhat sparse, so confidence is moderate.
From the tool's definition 'Point to a package.json or requirements.txt file to auto-discover libraries' — the tool reads a manifest file to discover/import library references
Attacks that exploit this kind of access
Point to a package.json or requirements.txt file to auto-discover libraries,. 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 auto_import_from_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 OmniDocs MCP. Nothing to install.
auto_import_from_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 auto_import_from_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 auto_import_from_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.
auto_import_from_manifest 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 →