check_malicious
Supply-chain malware check against OpenSSF/OSV. USE WHEN: about to suggest install of an unvetted/unfamiliar package; name came from a blog/tutorial. Call BEFORE check_package for untrusted pkgs. RETURNS: {is_malicious, threat_tier, source}.
This record as markdown: /tools/dev-depscope-mcp/check-malicious.md
What check_malicious does on Depscope
AI agents call check_malicious 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 | |
ecosystem | string | Yes |
Parameters from the server's own tool schema.
Why check_malicious is rated Low
This tool queries an external security database to classify package risk status. It retrieves information for decision-making but does not execute code, modify data, delete resources, or commit financial obligations. The low severity reflects that misuse would only result in incorrect threat assessment data being returned, not actual system compromise or data loss.
From the tool's definition Tool description states it performs a 'check' and 'RETURNS: {is_malicious, threat_tier, source}' — it retrieves and queries malware threat data from OpenSSF/OSV without modifying or executing anything.
Attacks that exploit this kind of access
The rule that runs check_malicious 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_malicious, this is the rule to start with:
check_malicious 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_malicious call is checked against it from then on.
Questions about check_malicious
Supply-chain malware check against OpenSSF/OSV. USE WHEN: about to suggest install of an unvetted/unfamiliar package; name came from a blog/tutorial. Call BEFORE check_package for untrusted pkgs. RETURNS: {is_malicious, threat_tier, source}. It is categorised as a Read tool in the Depscope MCP Server, which means it retrieves data without modifying state.
check_malicious accepts 2 parameters: package, 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_malicious: 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_malicious 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_malicious 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_malicious. 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_malicious 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