search_bundles

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/search-bundles.md

WHAT IT DOES

What search_bundles does on Trace

AI agents call search_bundles 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 search_bundles is rated Low

The tool searches pre-indexed dependency bundles and returns symbol definitions (like go-to-definition functionality). This is a retrieval operation that does not modify state, execute code, or trigger external side effects. It falls clearly into the Read category with low severity since it only provides code intelligence without mutation or operational risk.

From the tool's definition Tool performs 'search' and 'returns symbol definitions' from pre-indexed bundles — a read-only query operation with no side effects. No create, modify, delete, or execute capability mentioned.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs search_bundles 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 search_bundles, this is the rule to start with:

search_bundles Allowed

search_bundles 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": {
    "search_bundles": {}
  }
}

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 search_bundles call is checked against it from then on.

FAQ

Questions about search_bundles

What does the search_bundles tool do? +

Search pre-indexed bundles for symbols from popular libraries (React, Express, etc.). Returns symbol definitions from dependency bundles — useful for go-to-definition into node_modules/vendor. Install bundles via CLI:. 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 search_bundles? +

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

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

Can I rate-limit search_bundles? +

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

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

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

KEEP EXPLORING

More on Trace, and thousands of servers like it.

This server

All 191 Trace tools →

Across the catalogue

binary_search on 010 Editor →evaluate_search_quality on ACE-MCP →search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server → The MCP Attack Database →

Guides

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