filter_by_keyword

Filter log entries by keywords with support for multiple keywords and logical operations.

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-keyword.md

WHAT IT DOES

What filter_by_keyword does on CLIO Adios

AI agents call filter_by_keyword 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_keyword is rated Low

This tool performs filtering and analysis of existing log data, which is a retrieval operation with no side effects. It does not create, modify, delete data, execute code, or involve financial operations. The confidence is high because the description is clear and unambiguous about its read-only nature.

From the tool's definition Tool description states it "Filter[s] log entries by keywords" - a read-only query operation that retrieves a subset of existing log data based on search criteria. No modification, deletion, or execution of external code is implied.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs filter_by_keyword 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_keyword, this is the rule to start with:

filter_by_keyword Allowed

filter_by_keyword 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_keyword": {}
  }
}

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_keyword call is checked against it from then on.

FAQ

Questions about filter_by_keyword

What does the filter_by_keyword tool do? +

Filter log entries by keywords with support for multiple keywords and logical operations. 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_keyword? +

Register the CLIO Adios MCP server in PolicyLayer and add a rule for filter_by_keyword: 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_keyword? +

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

Can I rate-limit filter_by_keyword? +

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

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

filter_by_keyword 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

keyword_search on Azure AI Agent Service + Azure AI Search MCP Server → The MCP Attack Database →

Guides

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