Low Risk

get_visible_content

現在開いているページの表示領域内のコンテンツを取得します

How to control get_visible_content ↓

What get_visible_content does on Playwright MCP Server

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

Low Risk

Why get_visible_content needs a policy

The tool's function is to query and return visible page content without modifying, deleting, or executing anything. It is purely observational in nature, similar to other Read category tools on this server like get_interactive_elements and get_all_content. The blast radius of misuse is minimal as it only exposes already-rendered page content to the user.

From the tool's definition Tool retrieves visible content from the currently open page ("現在開いているページの表示領域内のコンテンツを取得します" translates to "Get content within the visible area of the currently open page"). This is a data retrieval operation with no side effects.

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

How to control get_visible_content

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

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

get_visible_content 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 Playwright MCP Server — 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 get_visible_content

What does the get_visible_content tool do? +

現在開いているページの表示領域内のコンテンツを取得します. It is categorised as a Read tool in the Playwright MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_visible_content? +

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

What risk level is get_visible_content? +

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

Can I rate-limit get_visible_content? +

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

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

get_visible_content is provided by the Playwright MCP Server MCP server (showfive/playwright-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Playwright MCP Server tool call.

Start from Playwright MCP Server, 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.

9 Playwright MCP Server 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.