Low Risk

get_runtime_metrics

获取运行时编排指标(请求总数、重试次数、挑战次数等)

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

AI agents call get_runtime_metrics 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_runtime_metrics 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_runtime_metrics:
    rules:
      - action: allow

See the full Chictr policy for all 9 tools.

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

View all 9 tools →

Agents calling read-class tools like get_runtime_metrics 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_runtime_metrics tool do? +

获取运行时编排指标(请求总数、重试次数、挑战次数等). 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_runtime_metrics? +

Add a rule in your Intercept YAML policy under the tools section for get_runtime_metrics. 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_runtime_metrics? +

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

Can I rate-limit get_runtime_metrics? +

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

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

get_runtime_metrics 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.