Low Risk

list_bundles

List installed pre-indexed bundles for dependency libraries. Shows package name, version, symbol/edge counts, and size. Read-only. Returns JSON: { bundles: [{ name, version, symbols, edges, size }], total }.

How to control list_bundles ↓

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

Low Risk

This is a pure read operation that queries and returns information about installed dependency library bundles. There is no data modification, code execution, deletion, or external side effects. The blast radius if misused by an agent is minimal—it only exposes static metadata about installed packages.

From the tool's definition Tool name 'list_bundles' and description explicitly states 'Read-only' and 'Returns JSON' listing metadata about pre-indexed bundles. Retrieves package information (name, version, counts, size) with no modification or side effects.

Documented attack patterns abuse exactly the kind of access list_bundles gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Trace, and nothing reaches the server without passing your rules. This is the rule we recommend for list_bundles:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_bundles": {}
  }
}

list_bundles is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Trace — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the list_bundles tool do? +

List installed pre-indexed bundles for dependency libraries. Shows package name, version, symbol/edge counts, and size. Read-only. Returns JSON: { bundles: [{ name, version, symbols, edges, size }], total }. 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 list_bundles? +

Register the Trace MCP server in PolicyLayer and add a rule for list_bundles: 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 list_bundles? +

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

Can I rate-limit list_bundles? +

Yes. Add a rate_limit block to the list_bundles 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 list_bundles completely? +

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

list_bundles 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.

Enforce policy on every Trace tool call.

Deterministic rules across all 178 Trace tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

178 Trace tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.