check_bulk
Fast pre-flight filter for a batch of (ecosystem, package) pairs. DB-only, <100ms for 100 items. USE WHEN: about to emit npm install a b c … or pip install a b c … — catches hallucinated names, stdlib, typos, and known-bad in ONE call. NOT a dep-tree audit (use scan_project for that). RETURNS: pe...
This record as markdown: /tools/dev-depscope-mcp/check-bulk.md
What check_bulk does on Depscope
AI agents call check_bulk 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 |
|---|---|---|---|
items | array | Yes |
Parameters from the server's own tool schema.
Why check_bulk is rated Low
check_bulk is a read-only query tool that retrieves package metadata and status information from a database. It has no side effects, does not modify data, does not execute code or shell commands, and does not delete anything. The tool is designed to validate package information before installation commands are issued, making it purely informational.
From the tool's definition Tool performs a 'fast pre-flight filter' and 'DB-only' query that 'RETURNS: per-item {status: exists|stdlib|malicious|typosquat_suspect|historical_incident|unknown}'.
Attacks that exploit this kind of access
The rule that runs check_bulk 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_bulk, this is the rule to start with:
check_bulk 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_bulk call is checked against it from then on.
Questions about check_bulk
Fast pre-flight filter for a batch of (ecosystem, package) pairs. DB-only, <100ms for 100 items. USE WHEN: about to emit npm install a b c … or pip install a b c … — catches hallucinated names, stdlib, typos, and known-bad in ONE call. NOT a dep-tree audit (use scan_project for that). RETURNS: per-item {status: exists|stdlib|malicious|typosquat_suspect|historical_incident|unknown}. It is categorised as a Read tool in the Depscope MCP Server, which means it retrieves data without modifying state.
check_bulk accepts 1 parameter: items. Required: items. 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_bulk: 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_bulk 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_bulk 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_bulk. 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_bulk 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