chrome_find_on_page
AI agents call chrome_find_on_page to retrieve information from WinScript without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The operation 'find_on_page' is a search function that locates text on a rendered webpage without modifying content, executing code, or triggering external operations. This is consistent with Read category tools. Confidence is moderately high despite empty description because the name and context from sibling tools strongly indicate a non-destructive query operation.
From the tool's definition Tool name 'chrome_find_on_page' indicates a search/query operation within a browser tab. Sibling tools like 'chrome_get_title' and 'chrome_get_url' are clearly Read operations, suggesting this tool follows the same pattern.
Documented attack patterns abuse exactly the kind of access chrome_find_on_page gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and WinScript, and nothing reaches the server without passing your rules. This is the rule we recommend for chrome_find_on_page:
{
"version": "1",
"default": "deny",
"tools": {
"chrome_find_on_page": {}
}
}chrome_find_on_page 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.
chrome_find_on_page. It is categorised as a Read tool in the WinScript MCP Server, which means it retrieves data without modifying state.
Register the WinScript MCP server in PolicyLayer and add a rule for chrome_find_on_page: 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 WinScript. Nothing to install.
chrome_find_on_page 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 chrome_find_on_page 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 chrome_find_on_page. 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.
chrome_find_on_page is provided by the WinScript MCP server (ravaniroshan/winscript-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from WinScript, 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.
17 WinScript tools catalogued and risk-classified — across an index of 43,000+ MCP servers.