get_package_deps

SERVERTrace SOURCEnikolai-vysotskyi/trace-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/nikolai-vysotskyi-trace-mcp/get-package-deps.md

WHAT IT DOES

What get_package_deps does on Trace

AI agents call get_package_deps to retrieve information from Trace without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_package_deps is rated Low

This tool retrieves and queries dependency information from source code repositories without creating, modifying, deleting, executing code, or causing any side effects. It is purely a data retrieval and analysis mechanism for understanding package dependencies in a cross-repo context.

From the tool's definition Tool description explicitly states 'Read-only' and 'Scans package.json/composer.json/pyproject.toml across all repos' to 'find which registered projects depend on a package' and 'what packages a project publishes'. Returns JSON data without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_package_deps safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Trace, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_package_deps, this is the rule to start with:

get_package_deps Allowed

get_package_deps is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_package_deps": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Trace, apply this rule, and every get_package_deps call is checked against it from then on.

FAQ

Questions about get_package_deps

What does the get_package_deps tool do? +

Cross-repo package dependency analysis: find which registered projects depend on a package, or what packages a project publishes. Scans package.json/composer.json/pyproject.toml across all repos in the registry. Use for cross-project dependency mapping. For impact of upgrading a specific package use plan_batch_change instead. Read-only. Returns JSON: { dependents, dependencies, package }. It is categorised as a Read tool in the Trace MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_package_deps? +

Register the Trace MCP server in PolicyLayer and add a rule for get_package_deps: 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 Trace. Nothing to install.

What risk level is get_package_deps? +

get_package_deps is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_package_deps? +

Yes. Add a rate_limit block to the get_package_deps 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.

How do I block get_package_deps completely? +

Set action: deny in the PolicyLayer policy for get_package_deps. 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.

What MCP server provides get_package_deps? +

get_package_deps is provided by the Trace MCP server (nikolai-vysotskyi/trace-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Trace, and thousands of servers like it.

This server

All 191 Trace tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server →get_customer_data on 08-AI-Business-Agent → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →