This record as markdown: /tools/io-github-kivanccakmak-yaver/log-search.md
What log_search does on Yaver
AI agents call log_search to retrieve information from Yaver without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
q | string | Yes | |
limit | number | — | |
services | string | — |
Parameters from the server's own tool schema.
Why log_search is rated Low
This tool retrieves and searches existing log data using full-text search (FTS5). It performs read-only queries against an index and returns results without creating, modifying, or deleting data. The search operation has no side effects and fits squarely within the Read category. Severity is low because log access may reveal sensitive information but the tool itself cannot alter state or execute operations.
From the tool's definition Tool name 'log_search' and description 'Search all indexed container logs via SQLite FTS5' indicate a query/search operation with no mutation capability.
Attacks that exploit this kind of access
The rule that runs log_search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For log_search, this is the rule to start with:
log_search is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every log_search call is checked against it from then on.
Questions about log_search
Search all indexed container logs via SQLite FTS5. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
log_search accepts 3 parameters: q, limit, services. Required: q. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver MCP server in PolicyLayer and add a rule for log_search: 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 Yaver. Nothing to install.
log_search is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the log_search 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.
Set action: deny in the PolicyLayer policy for log_search. 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.
log_search is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Yaver, and thousands of servers like it.
This server
Across the catalogue