Low Risk

find_text

find_text

How to control find_text ↓

AI agents call find_text to retrieve information from Tree Sitter without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

The tool performs text search/retrieval operations on code, which is a read-only action with no data modification or command execution. Despite empty description, the naming pattern and server purpose (code analysis) strongly indicate this is a query/search capability. Severity is low because searching code has minimal blast radius—it cannot execute, modify, or delete data.

From the tool's definition Tool name 'find_text' suggests searching/locating text within code; context indicates tree-sitter code analysis server designed for querying codebases. Similar sibling tools like 'find_usage' and 'find_similar_code' are clearly read-only search operations.

Documented attack patterns abuse exactly the kind of access find_text gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Tree Sitter, and nothing reaches the server without passing your rules. This is the rule we recommend for find_text:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "find_text": {}
  }
}

find_text is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Tree Sitter — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the find_text tool do? +

find_text. It is categorised as a Read tool in the Tree Sitter MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on find_text? +

Register the Tree Sitter MCP server in PolicyLayer and add a rule for find_text: 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 Tree Sitter. Nothing to install.

What risk level is find_text? +

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

Can I rate-limit find_text? +

Yes. Add a rate_limit block to the find_text 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 find_text completely? +

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

find_text is provided by the Tree Sitter MCP server (wrale/mcp-server-tree-sitter). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Tree Sitter tool call.

Deterministic rules across all 26 Tree Sitter tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

26 Tree Sitter tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.