search_content
Search for text content inside files (like grep/ripgrep). Returns matching lines with file paths and line numbers.
This record as markdown: /tools/io-github-kivanccakmak-yaver/search-content.md
What search_content does on Yaver
AI agents call search_content 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 |
|---|---|---|---|
query | string | Yes | Text or regex to search for |
directory | string | — | Directory to search in (default: agent work dir) |
max_results | integer | — | Max results (default: 30) |
Parameters from the server's own tool schema.
Why search_content is rated Low
The tool retrieves and displays matching text from files without modifying, deleting, or executing anything. It is analogous to grep/ripgrep, which are read-only search utilities. No data is created, destroyed, or altered. The blast radius of misuse is minimal—an agent could only learn what content exists in files, not act upon it destructively.
From the tool's definition Tool description states it 'Search[es] for text content inside files (like grep/ripgrep). Returns matching lines with file paths and line numbers.' This is a query/search operation with no side effects.
Risk signalsAccepts file system path (directory)
Attacks that exploit this kind of access
The rule that runs search_content 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 search_content, this is the rule to start with:
search_content 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 search_content call is checked against it from then on.
Questions about search_content
Search for text content inside files (like grep/ripgrep). Returns matching lines with file paths and line numbers. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
search_content accepts 3 parameters: query, directory, max_results. Required: query. 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 search_content: 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.
search_content 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 search_content 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 search_content. 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.
search_content 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