List all package manager files found in a project.
AI agents call list_package_managers to retrieve information from License Scanner MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs discovery and enumeration of existing package manager configurations (e.g., package.json, requirements.txt, Cargo.toml) without modifying, executing, or deleting any data. It is a straightforward query operation that retrieves directory/file metadata.
From the tool's definition Tool 'list_package_managers' lists package manager files found in a project. The verb 'list' and the read-only nature of file discovery indicate retrieval of information with no side effects.
Attacks that exploit this kind of access
List all package manager files found in a project. It is categorised as a Read tool in the License Scanner MCP Server MCP Server, which means it retrieves data without modifying state.
Register the License Scanner MCP Server MCP server in PolicyLayer and add a rule for list_package_managers: 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 License Scanner MCP Server. Nothing to install.
list_package_managers 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 list_package_managers 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 list_package_managers. 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.
list_package_managers is provided by the License Scanner MCP Server MCP server (ryancadby/mcp-license-scanner). 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 →