Low Risk

get_cache_stats_v2

获取双层缓存统计(L1内存 + L2 SQLite)

Part of the Chictr MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents call get_cache_stats_v2 to retrieve information from Chictr 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_cache_stats_v2 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.

chictr.yaml
tools:
  get_cache_stats_v2:
    rules:
      - action: allow

See the full Chictr policy for all 9 tools.

Tool Name get_cache_stats_v2
Category Read
MCP Server Chictr MCP Server
Risk Level Low

View all 9 tools →

Agents calling read-class tools like get_cache_stats_v2 have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the get_cache_stats_v2 tool do? +

获取双层缓存统计(L1内存 + L2 SQLite). It is categorised as a Read tool in the Chictr MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_cache_stats_v2? +

Add a rule in your Intercept YAML policy under the tools section for get_cache_stats_v2. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Chictr MCP server.

What risk level is get_cache_stats_v2? +

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

Can I rate-limit get_cache_stats_v2? +

Yes. Add a rate_limit block to the get_cache_stats_v2 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.

How do I block get_cache_stats_v2 completely? +

Set action: deny in the Intercept policy for get_cache_stats_v2. 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_cache_stats_v2? +

get_cache_stats_v2 is provided by the Chictr MCP server (chictr-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Chictr

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.