Search text patterns within file contents using regex. Returns matching line numbers and context - use with read_file/read_multiple_files to retrieve actual content.
AI agents call grep_files to retrieve information from Vulcan File Ops without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
grep_files is a search/query operation that retrieves information about file contents without modifying, executing code, or deleting data. It has no side effects beyond the read operation itself. The low severity reflects minimal blast radius—worst case an attacker learns about file contents they may already have access to.
From the tool's definition Tool description states it "Search[es] text patterns within file contents" and "Returns matching line numbers and context".
Documented attack patterns abuse exactly the kind of access grep_files gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Vulcan File Ops, and nothing reaches the server without passing your rules. This is the rule we recommend for grep_files:
{
"version": "1",
"default": "deny",
"tools": {
"grep_files": {}
}
}grep_files is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Search text patterns within file contents using regex. Returns matching line numbers and context - use with read_file/read_multiple_files to retrieve actual content. It is categorised as a Read tool in the Vulcan File Ops MCP Server, which means it retrieves data without modifying state.
Register the Vulcan File Ops MCP server in PolicyLayer and add a rule for grep_files: 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 Vulcan File Ops. Nothing to install.
grep_files 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 grep_files 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 grep_files. 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.
grep_files is provided by the Vulcan File Ops MCP server (n0zer0d4y/vulcan-file-ops). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Vulcan File Ops, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
15 Vulcan File Ops tools catalogued and risk-classified — across an index of 43,000+ MCP servers.