Find pattern in file with line numbers and optional context lines.
AI agents call find_in_file to retrieve information from TermPipe MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs pattern matching and returns results with context; it has no side effects on the file system, does not execute code, and does not modify or delete data. It is a straightforward read operation analogous to grep or find utilities. While the parent server offers terminal access (a high-risk capability), this specific tool is confined to non-destructive information retrieval.
From the tool's definition The tool description explicitly states it 'Find[s] pattern in file with line numbers and optional context lines' — a pure search/query operation that retrieves data without modifying, deleting, or executing code.
Attacks that exploit this kind of access
Find pattern in file with line numbers and optional context lines. It is categorised as a Read tool in the TermPipe MCP MCP Server, which means it retrieves data without modifying state.
Register the TermPipe MCP server in PolicyLayer and add a rule for find_in_file: 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 TermPipe MCP. Nothing to install.
find_in_file 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 find_in_file 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 find_in_file. 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.
find_in_file is provided by the TermPipe MCP server (wbind-core/termpipe-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →