Get the TLI (Theme Lifecycle Index) algorithm methodology — how scores, stages, and predictions work. Use when the user asks: - How are theme scores calculated? - What do the lifecycle stages mean? - How does the prediction work? - What data sources, schedules, runtime pipeline, or database tabl...
Part of the Stockmatrix MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call get_methodology to retrieve information from Stockmatrix 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 get_methodology 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:
get_methodology:
rules:
- action: allow See the full Stockmatrix policy for all 10 tools.
Agents calling read-class tools like get_methodology 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.
Get the TLI (Theme Lifecycle Index) algorithm methodology — how scores, stages, and predictions work. Use when the user asks: - How are theme scores calculated? - What do the lifecycle stages mean? - How does the prediction work? - What data sources, schedules, runtime pipeline, or database tables power TLI? - TLI 알고리즘 설명, 점수 산출 방식, 단계 판정 기준 - What data sources are used? - TLI 수집 파이프라인, 업데이트 주기, 비교 파이프라인, 데이터 테이블 Returns structured documentation of the scoring algorithm, data collection pipeline, runtime orchestration, database tables, stage determination, stabilization techniques, comparison analysis, and prediction methodology.. It is categorised as a Read tool in the Stockmatrix MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for get_methodology. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Stockmatrix MCP server.
get_methodology 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 get_methodology 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 get_methodology. 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.
get_methodology is provided by the Stockmatrix MCP server (stockmatrix-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