Low Risk

compression_ratio

Set target compression ratio

Part of the MCP Search Server server.

compression_ratio 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 MCP SEARCH SERVER →

Free to start. No card required.

AI agents call compression_ratio to retrieve information from MCP Search Server 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.

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

See the full MCP Search Server policy for all 20 tools.

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

ENFORCE ON MY MCP SEARCH SERVER →

View all 20 tools →

These attack patterns abuse exactly the kind of access compression_ratio 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 compression_ratio only ever does what you allow.

SECURE MCP SEARCH SERVER →

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

What does the compression_ratio tool do? +

Set target compression ratio. It is categorised as a Read tool in the MCP Search Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on compression_ratio? +

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

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 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 compression_ratio completely? +

Set action: deny in the PolicyLayer 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 MCP Search Server MCP server (KazKozDev/mcp-search-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP Search Server tool call.

Deterministic rules across all 20 MCP Search Server 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.