search_files

Search for text across files in the workspace. Returns matching lines with context.

SERVERTerminal Guardian SOURCE7majesty-m/terminal-guardian-mcp

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/7majesty-m-terminal-guardian-mcp/search-files.md

WHAT IT DOES

What search_files does on Terminal Guardian

AI agents call search_files to retrieve information from Terminal Guardian without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why search_files is rated Low

This tool performs a read-only search operation across files, returning matching results. It has no ability to modify, execute, delete, or move data. The only potential risk is information disclosure if sensitive data patterns are searched, but the tool itself is fundamentally a query/search utility with no side effects. Low severity due to sandboxed workspace context and read-only nature.

From the tool's definition Tool description states 'Search for text across files' and 'Returns matching lines with context' — purely retrieval operations with no modification, deletion, or execution capabilities.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs search_files safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Terminal Guardian, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search_files, this is the rule to start with:

search_files Allowed

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Terminal Guardian, apply this rule, and every search_files call is checked against it from then on.

FAQ

Questions about search_files

What does the search_files tool do? +

Search for text across files in the workspace. Returns matching lines with context. It is categorised as a Read tool in the Terminal Guardian MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_files? +

Register the Terminal Guardian MCP server in PolicyLayer and add a rule for search_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 Terminal Guardian. Nothing to install.

What risk level is search_files? +

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

Can I rate-limit search_files? +

Yes. Add a rate_limit block to the search_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.

How do I block search_files completely? +

Set action: deny in the PolicyLayer policy for search_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.

What MCP server provides search_files? +

search_files is provided by the Terminal Guardian MCP server (7majesty-m/terminal-guardian-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Terminal Guardian, and thousands of servers like it.

This server

All 25 Terminal Guardian tools →

Across the catalogue

search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server →search_circuits on 0gzk → The MCP Attack Database →

Guides

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