Open an interactive project tree viewer in the browser. Shows the indexed file structure with clickable nodes - click on a file to see its signature (header comments, types, methods). Uses a local HTTP server with WebSocket for live updates.
Accepts file system path (path)
Part of the Aidex MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call aidex_viewer to retrieve information from Aidex without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though aidex_viewer only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
aidex_viewer:
rules:
- action: allowSee the full Aidex policy for all 29 tools.
Agents calling read-class tools like aidex_viewer have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Open an interactive project tree viewer in the browser. Shows the indexed file structure with clickable nodes - click on a file to see its signature (header comments, types, methods). Uses a local HTTP server with WebSocket for live updates.. It is categorised as a Read tool in the Aidex MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for aidex_viewer. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Aidex MCP server.
aidex_viewer 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 aidex_viewer rule in your Intercept 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 Intercept policy for aidex_viewer. 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.
aidex_viewer is provided by the Aidex MCP server (aidex-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept