Browse stored analysis outputs on the server. Call this FIRST before get_file to discover what files are available. This is the recommended starting point when the user asks about a specific ticker's analysis — check what's already cached before running a new analysis. Each analysis produces 7...
Single-target operation
Part of the Technical Analysis MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call analysis_list_files to retrieve information from Technical Analysis 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 analysis_list_files 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:
analysis_list_files:
rules:
- action: allowSee the full Technical Analysis policy for all 11 tools.
Agents calling read-class tools like analysis_list_files 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.
Browse stored analysis outputs on the server. Call this FIRST before get_file to discover what files are available. This is the recommended starting point when the user asks about a specific ticker's analysis — check what's already cached before running a new analysis. Each analysis produces 7 files per ticker: - 2 chart images (daily + weekly PNG) - 3 analysis reports (daily, weekly, comparative TXT) - 2 data files (daily + weekly CSV with OHLCV + indicators) Cached OHLCV files are stored in cache/ohlcv/{market}/ and auto-cleaned daily at market-specific times. Output result files in output/ are auto-cleaned after 7 days. Args: ticker: Optional. If omitted, lists all tickers that have been analyzed. If provided, lists all available files for that ticker with sizes. Returns: Without ticker: summary of all ticker folders. With ticker: detailed file listing with types and sizes. . It is categorised as a Read tool in the Technical Analysis MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for analysis_list_files. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Technical Analysis MCP server.
analysis_list_files 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 analysis_list_files 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 analysis_list_files. 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.
analysis_list_files is provided by the Technical Analysis MCP server (ta-mcp/technical-analysis-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