現在開いているページの表示領域内のコンテンツを取得します
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.
This tool performs a read-only operation—it queries and returns the visible content of a web page without side effects. It does not create, modify, delete, or execute anything. Alongside sibling tools like navigate and mouse_click which are Execute category, this read operation poses minimal risk if misused by an agent, as the worst outcome is information disclosure of already-visible page content.
From the tool's definition get_visible_content retrieves content from the currently open page's visible area. The description states it 'retrieves (取得します) content' from the visible region, with no modification, deletion, or execution capability.
Attacks that exploit this kind of access
現在開いているページの表示領域内のコンテンツを取得します. It is categorised as a Read tool in the Playwright MCP Server MCP Server, which means it retrieves data without modifying state.
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.
get_visible_content 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 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.
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.
get_visible_content is provided by the Playwright MCP Server MCP server (kotelberg/playwright-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →