compare_packages
Side-by-side comparison (health, vulns, downloads, maintainers, last release) of 2-10 packages in the same ecosystem. USE WHEN: 'X vs Y' / 'should I pick X or Y'. RETURNS: table-shaped JSON, one row per package.
This record as markdown: /tools/dev-depscope-mcp/compare-packages.md
What compare_packages does on Depscope
AI agents call compare_packages to retrieve information from Depscope without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
packages | array | Yes | Package names to compare, e.g. ['express','fastify','hono']. |
ecosystem | string | Yes |
Parameters from the server's own tool schema.
Why compare_packages is rated Low
This tool retrieves and presents existing package information for comparative analysis. It has no side effects: it does not modify packages, execute code, delete data, or commit financial obligations. The use case ('X vs Y' / 'should I pick X or Y') confirms it is a read-only decision-support tool.
From the tool's definition Tool performs 'side-by-side comparison' and 'RETURNS: table-shaped JSON, one row per package' — retrieval and display of package metadata (health, vulns, downloads, maintainers, last release) with no modification, creation, or deletion of data.
Attacks that exploit this kind of access
The rule that runs compare_packages safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Depscope, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For compare_packages, this is the rule to start with:
compare_packages is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Depscope, apply this rule, and every compare_packages call is checked against it from then on.
Questions about compare_packages
Side-by-side comparison (health, vulns, downloads, maintainers, last release) of 2-10 packages in the same ecosystem. USE WHEN: 'X vs Y' / 'should I pick X or Y'. RETURNS: table-shaped JSON, one row per package. It is categorised as a Read tool in the Depscope MCP Server, which means it retrieves data without modifying state.
compare_packages accepts 2 parameters: packages, ecosystem. Required: packages, ecosystem. The full parameter table on this page comes from the server's own tool schema.
Register the Depscope MCP server in PolicyLayer and add a rule for compare_packages: 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 Depscope. Nothing to install.
compare_packages 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 compare_packages 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 compare_packages. 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.
compare_packages is provided by the Depscope MCP server (cuttalo/depscope-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Depscope, and thousands of servers like it.
This server
Across the catalogue