Low Risk

get_theme_history

Get 30-day score history for a Korean stock theme. Returns daily TLI scores and stage transitions for trend analysis. Use when the user asks about theme momentum over time, whether a theme is gaining or losing interest, or wants to see historical trajectory. Answers: "이 테마 추세가 어때?", "최근 한달 흐름", "...

Part of the Stockmatrix server.

get_theme_history is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE STOCKMATRIX →

Free to start. No card required.

AI agents call get_theme_history 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_theme_history 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.

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

See the full Stockmatrix policy for all 10 tools.

Get this rule live on your own Stockmatrix server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY STOCKMATRIX →

View all 10 tools →

These attack patterns abuse exactly the kind of access get_theme_history gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so get_theme_history only ever does what you allow.

SECURE STOCKMATRIX →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the get_theme_history tool do? +

Get 30-day score history for a Korean stock theme. Returns daily TLI scores and stage transitions for trend analysis. Use when the user asks about theme momentum over time, whether a theme is gaining or losing interest, or wants to see historical trajectory. Answers: "이 테마 추세가 어때?", "최근 한달 흐름", "is this theme gaining or losing momentum?", "show me the trend".. It is categorised as a Read tool in the Stockmatrix MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_theme_history? +

Register the Stockmatrix MCP server in PolicyLayer and add a rule for get_theme_history: 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 Stockmatrix. Nothing to install.

What risk level is get_theme_history? +

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

Can I rate-limit get_theme_history? +

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

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

get_theme_history is provided by the Stockmatrix MCP server (stockmatrix-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Stockmatrix tool call.

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

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.