package_trust
Use before recommending or installing an npm package — to check whether it is safe and current. Pass the package name (and optionally a version, e.g. 4.17.0) with language='ts'. The substrate returns every OSV/GHSA security advisory affecting it (with severity, CVE aliases, the exact affected ver...
This record as markdown: /tools/dev-codeitall-codeitall/package-trust.md
What package_trust does on Codeitall
AI agents call package_trust to retrieve information from Codeitall 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 | |
version | string | — | |
language | string | — |
Parameters from the server's own tool schema.
Why package_trust is rated Low
This tool retrieves and aggregates publicly available security and registry data about packages. It does not install packages, execute code, modify data, delete resources, or commit financial obligations. While the information could inform security decisions, the tool itself only performs read operations against npm registry and vulnerability databases.
From the tool's definition Tool queries security advisories, deprecation status, and registry metadata for npm packages. Description states it returns 'every OSV/GHSA security advisory', 'deprecation' status, 'latest version and last-publish date', and other registry signals.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs package_trust safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Codeitall, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For package_trust, this is the rule to start with:
package_trust 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 Codeitall, apply this rule, and every package_trust call is checked against it from then on.
Questions about package_trust
Use before recommending or installing an npm package — to check whether it is safe and current. Pass the package name (and optionally a version, e.g. 4.17.0) with language='ts'. The substrate returns every OSV/GHSA security advisory affecting it (with severity, CVE aliases, the exact affected version range, and the advisory URL) and, if you pass a version, whether THAT version is affected; plus npm registry signals — whether the package is deprecated (and the maintainer's deprecation message), its latest version and last-publish date, and a maintained flag; plus how many real Next.js projects in the corpus depend on it and which declared version ranges the advisories actually bite. This is the cross-referenced security + maintenance signal a stale model cannot reliably know. It is categorised as a Read tool in the Codeitall MCP Server, which means it retrieves data without modifying state.
package_trust accepts 3 parameters: package, version, language. Required: package. The full parameter table on this page comes from the server's own tool schema.
Register the Codeitall MCP server in PolicyLayer and add a rule for package_trust: 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 Codeitall. Nothing to install.
package_trust 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 package_trust 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 package_trust. 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.
package_trust is provided by the Codeitall MCP server (https://api.codeitall.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Codeitall, and thousands of servers like it.
This server
Across the catalogue