Low Risk

find_text

find_text

How to control find_text ↓

What find_text does on Openowl

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

Low Risk

Why find_text needs a policy

Find/search operations are read-only by nature—they locate and retrieve text from the screen without side effects. The low severity reflects minimal blast radius even if an AI agent locates unintended text, as no data is modified or deleted. Confidence is slightly reduced due to the empty description, but the function name and server context strongly indicate a retrieval operation.

From the tool's definition Tool name is 'find_text' with no description provided. Based on the server's stated purpose of providing 'screenshots, clicking, typing, OCR, window management, accessibility-tree queries', a find_text tool fits the pattern of query/search operations that…

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

How to control find_text

PolicyLayer is an MCP gateway — it sits between your AI agents and Openowl, 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 Openowl — 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.

Related tools and policies

Go deeper

Questions about find_text

What does the find_text tool do? +

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

How do I enforce a policy on find_text? +

Register the Openowl 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 Openowl. 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 Openowl MCP server (mihir-kanzariya/openowl). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Openowl tool call.

Start from Openowl, 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.

40 Openowl tools catalogued and risk-classified — across an index of 43,000+ 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.