check_package
Full machine-readable JSON report (~2k tokens). USE WHEN: you need to programmatically parse specific fields (CI gating, UI, sub-field extraction). Otherwise prefer get_package_prompt. RETURNS: {package, health:{score}, vulnerabilities[], latest, deprecated, maintainers, recommendation}.
This record as markdown: /tools/dev-depscope-mcp/check-package.md
What check_package does on Depscope
AI agents call check_package 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 |
|---|---|---|---|
package | string | Yes | Package name (e.g. 'express', 'fastapi', 'serde'). |
version | string | — | Specific version (optional; default = latest). |
ecosystem | string | Yes |
Parameters from the server's own tool schema.
Why check_package is rated Low
This tool retrieves and queries package metadata and security information without creating, modifying, deleting, or executing anything. It is a read-only data access operation that returns information for analysis and decision-making, fitting squarely into the Read category with low severity since misuse would only result in accessing already-public package information.
From the tool's definition Tool returns a 'Full machine-readable JSON report' with fields like health score, vulnerabilities, latest version, maintainers, and recommendation.
Attacks that exploit this kind of access
The rule that runs check_package 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 check_package, this is the rule to start with:
check_package 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 check_package call is checked against it from then on.
Questions about check_package
Full machine-readable JSON report (~2k tokens). USE WHEN: you need to programmatically parse specific fields (CI gating, UI, sub-field extraction). Otherwise prefer get_package_prompt. RETURNS: {package, health:{score}, vulnerabilities[], latest, deprecated, maintainers, recommendation}. It is categorised as a Read tool in the Depscope MCP Server, which means it retrieves data without modifying state.
check_package accepts 3 parameters: package, version, ecosystem. Required: package, 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 check_package: 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.
check_package 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 check_package 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 check_package. 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.
check_package 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