AI agents call fs_search to retrieve information from Taw Computer without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
fs_search is a pure query/search operation analogous to listing or fetching data. It has no side effects—it only reads and returns matching content. The low severity reflects that information disclosure risk is minimal in a sandboxed Ubuntu container environment, and grep operations cannot corrupt or alter data.
From the tool's definition Tool performs 'grep -rn' which searches for text patterns in files. This is a read-only operation that retrieves matching lines from files without modifying them.
Documented attack patterns abuse exactly the kind of access fs_search gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Taw Computer, and nothing reaches the server without passing your rules. This is the rule we recommend for fs_search:
{
"version": "1",
"default": "deny",
"tools": {
"fs_search": {}
}
}fs_search 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.
grep -rn for a pattern in a directory. It is categorised as a Read tool in the Taw Computer MCP Server, which means it retrieves data without modifying state.
Register the Taw Computer MCP server in PolicyLayer and add a rule for fs_search: 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 Taw Computer. Nothing to install.
fs_search 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 fs_search 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 fs_search. 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.
fs_search is provided by the Taw Computer MCP server (tawgroup/taw-computer). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Taw Computer, 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.
36 Taw Computer tools catalogued and risk-classified — across an index of 43,000+ MCP servers.