get_package_prompt
LLM-optimised package brief — plain text ~300 tokens (~75% cheaper than JSON). Verdict (SAFE/AVOID/URGENT/MALICIOUS) + health + vulns + alternatives + maintainer alerts. USE WHEN: you want to reason over a package and drop the output directly in context; 'is X safe'. PREFER THIS over check_packag...
This record as markdown: /tools/dev-depscope-mcp/get-package-prompt.md
What get_package_prompt does on Depscope
AI agents call get_package_prompt 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_package_prompt is rated Low
This tool performs a read-only query of package metadata and security information. It retrieves pre-computed verdicts, health scores, vulnerability data, and maintainer alerts—all informational outputs. There are no side effects, no data modification, no code execution, and no financial impact.
From the tool's definition Tool name and description indicate it 'LLM-optimised package brief' that returns 'plain text ~300 tokens' with 'Verdict (SAFE/AVOID/URGENT/MALICIOUS) + health + vulns + alternatives + maintainer alerts.' It retrieves and queries package information without…
Attacks that exploit this kind of access
The rule that runs get_package_prompt 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_package_prompt, this is the rule to start with:
get_package_prompt 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_package_prompt call is checked against it from then on.
Questions about get_package_prompt
LLM-optimised package brief — plain text ~300 tokens (~75% cheaper than JSON). Verdict (SAFE/AVOID/URGENT/MALICIOUS) + health + vulns + alternatives + maintainer alerts. USE WHEN: you want to reason over a package and drop the output directly in context; 'is X safe'. PREFER THIS over check_package in 95% of LLM cases. RETURNS: plain-text brief. It is categorised as a Read tool in the Depscope MCP Server, which means it retrieves data without modifying state.
get_package_prompt 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_package_prompt: 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_package_prompt 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_package_prompt 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_package_prompt. 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_package_prompt 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