get_health_score
Single 0-100 health score — cheapest go/no-go gate (>=70 safe). USE WHEN: CI gating or pkg already screened for malware/typos. NOT a first screen — run check_malicious + check_typosquat first. For a verbal verdict use get_package_prompt. RETURNS: {score, verdict}.
This record as markdown: /tools/dev-depscope-mcp/get-health-score.md
What get_health_score does on Depscope
AI agents call get_health_score 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 get_health_score is rated Low
This tool purely queries and retrieves data (a health score and verdict) with no side effects. It does not create, modify, delete, or execute any operations. The description emphasizes it should be used after other checks (check_malicious, check_typosquat) are run, confirming it is a read-only assessment tool.
From the tool's definition Tool description explicitly states it 'RETURNS: {score, verdict}' and is described as a 'go/no-go gate' that retrieves a pre-calculated health score. No creation, modification, deletion, or execution of external operations is mentioned.
Attacks that exploit this kind of access
The rule that runs get_health_score 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 get_health_score, this is the rule to start with:
get_health_score 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 get_health_score call is checked against it from then on.
Questions about get_health_score
Single 0-100 health score — cheapest go/no-go gate (>=70 safe). USE WHEN: CI gating or pkg already screened for malware/typos. NOT a first screen — run check_malicious + check_typosquat first. For a verbal verdict use get_package_prompt. RETURNS: {score, verdict}. It is categorised as a Read tool in the Depscope MCP Server, which means it retrieves data without modifying state.
get_health_score 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 get_health_score: 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.
get_health_score 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 get_health_score 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 get_health_score. 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.
get_health_score 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