filter_by_log_level

Filter log entries by log level (ERROR, WARN, INFO, DEBUG, etc.).

SERVERCLIO Adios SOURCEpypi:clio-kit

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-iowarp-adios-mcp/filter-by-log-level.md

WHAT IT DOES

What filter_by_log_level does on CLIO Adios

AI agents call filter_by_log_level to retrieve information from CLIO Adios without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why filter_by_log_level is rated Low

This tool retrieves and filters log entries based on log level criteria. It performs no modifications, deletions, code execution, or external operations. It is a straightforward data retrieval and analysis task, consistent with Read category. Severity is low because misuse would only expose or organize existing log data without causing harm.

From the tool's definition Tool description states 'Filter log entries by log level' — a pure filtering/querying operation on existing log data with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs filter_by_log_level safely

PolicyLayer is an MCP gateway: it sits between your AI agents and CLIO Adios, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For filter_by_log_level, this is the rule to start with:

filter_by_log_level Allowed

filter_by_log_level is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "filter_by_log_level": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect CLIO Adios, apply this rule, and every filter_by_log_level call is checked against it from then on.

FAQ

Questions about filter_by_log_level

What does the filter_by_log_level tool do? +

Filter log entries by log level (ERROR, WARN, INFO, DEBUG, etc.). It is categorised as a Read tool in the CLIO Adios MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on filter_by_log_level? +

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

What risk level is filter_by_log_level? +

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

Can I rate-limit filter_by_log_level? +

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

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

filter_by_log_level is provided by the CLIO Adios MCP server (pypi:clio-kit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on CLIO Adios, and thousands of servers like it.

This server

All 204 CLIO Adios tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →