Low Risk

chrome_get_title

chrome_get_title

How to control chrome_get_title ↓

What chrome_get_title does on WinScript

AI agents call chrome_get_title 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.

Low Risk

Why chrome_get_title needs a policy

This tool retrieves metadata (page title) from an already-open Chrome tab without creating, modifying, or deleting data. It has no side effects and falls clearly into the Read category. Severity is low because page titles contain minimal sensitive information and the operation is non-destructive.

From the tool's definition Tool name 'chrome_get_title' indicates retrieval of page title from Chrome browser. The verb 'get' is a read operation. Empty description is uninformative, but the name strongly suggests querying browser state without modification.

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

How to control chrome_get_title

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_get_title:

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

chrome_get_title 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 WinScript — 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 chrome_get_title

What does the chrome_get_title tool do? +

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

How do I enforce a policy on chrome_get_title? +

Register the WinScript MCP server in PolicyLayer and add a rule for chrome_get_title: 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.

What risk level is chrome_get_title? +

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

Can I rate-limit chrome_get_title? +

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

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

chrome_get_title 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.

Enforce policy on every WinScript tool call.

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.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.