Low Risk

compression_ratio

Get token reduction ratio

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

semantic-frame Read Risk 2/5

AI agents call compression_ratio to retrieve information from Semantic Frame 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 compression_ratio 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.

io-github-anarkitty1-semantic-frame.yaml
tools:
  compression_ratio:
    rules:
      - action: allow

See the full Semantic Frame policy for all 18 tools.

Tool Name compression_ratio
Category Read
Risk Level Low

View all 18 tools →

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

Get token reduction ratio. It is categorised as a Read tool in the Semantic Frame MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on compression_ratio? +

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

What risk level is compression_ratio? +

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

Can I rate-limit compression_ratio? +

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

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

compression_ratio is provided by the Semantic Frame MCP server (semantic-frame). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Semantic Frame

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.