ページ内のインタラクティブ要素（ボタン、テキストエリア、ラジオボタンなど）の座標と範囲を取得します
AI agents call get_interactive_elements 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 information retrieval about page elements without modifying any data or triggering actions. It queries the DOM structure to identify and locate interactive components, returning their positions. This is a passive read operation that enables informed decision-making for subsequent interactions but causes no state changes itself.
From the tool's definition Tool retrieves interactive element coordinates and ranges ('ページ内のインタラクティブ要素...の座標と範囲を取得します'), which is a query operation with no side effects.
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_interactive_elements: 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_interactive_elements 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_interactive_elements 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_interactive_elements. 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_interactive_elements 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 →