get_trust_signals
One-call aggregate of ALL non-CVE supply-chain trust signals: maintainer trust (bus factor, ownership changes), OpenSSF Scorecard, quality (criticality, release velocity, publish security), and SLSA/Sigstore provenance. USE WHEN: deep-vetting a package beyond CVEs (hardened/regulated env, SBOM/co...
This record as markdown: /tools/dev-depscope-mcp/get-trust-signals.md
What get_trust_signals does on Depscope
AI agents call get_trust_signals 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_trust_signals is rated Low
This tool queries and aggregates pre-computed security metadata (maintainer trust, OpenSSF Scorecard, quality metrics, provenance) from multiple backends. It retrieves and displays data for decision-making with no side effects. The parallelization is internal query optimization, not code execution or state mutation.
From the tool's definition Tool description uses 'aggregate', 'signals', 'vetting', 'review', and 'RETURNS' data structures—no modification, deletion, or execution of code.
Attacks that exploit this kind of access
The rule that runs get_trust_signals 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_trust_signals, this is the rule to start with:
get_trust_signals 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_trust_signals call is checked against it from then on.
Questions about get_trust_signals
One-call aggregate of ALL non-CVE supply-chain trust signals: maintainer trust (bus factor, ownership changes), OpenSSF Scorecard, quality (criticality, release velocity, publish security), and SLSA/Sigstore provenance. USE WHEN: deep-vetting a package beyond CVEs (hardened/regulated env, SBOM/compliance, small-pkg ownership review, choosing between healthy candidates). Runs 4 backend endpoints in parallel. RETURNS: {maintainer, scorecard, quality, provenance} — each may be null if its backend call failed. It is categorised as a Read tool in the Depscope MCP Server, which means it retrieves data without modifying state.
get_trust_signals 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_trust_signals: 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_trust_signals 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_trust_signals 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_trust_signals. 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_trust_signals 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