Search for text content within files in the workspace
AI agents call search_files to retrieve information from MCP Workspace Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries data (text content) from files without creating, modifying, or deleting anything. It has no capacity to alter state or trigger external operations. The sandboxed workspace context further limits blast radius. Confidence is high because the description is explicit about the read-only nature of the operation.
From the tool's definition Tool name is 'search_files' and description states it will 'Search for text content within files in the workspace' — a read-only operation with no modification or side effects.
Attacks that exploit this kind of access
Search for text content within files in the workspace. It is categorised as a Read tool in the MCP Workspace Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Workspace Server 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 MCP Workspace Server. Nothing to install.
search_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 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.
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.
search_files is provided by the MCP Workspace Server MCP server (shayyeffet/ultimate_mcp_server). 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 →