checks if an element is visible on the page
AI agents call is_element_displayed to retrieve information from Selenium MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves visibility status information about a DOM element. It has no side effects—it does not modify the page, execute code, delete data, or commit financial transactions. It is a passive inspection/query operation, consistent with the Read category for tools that retrieve or query data without side effects.
From the tool's definition The tool 'is_element_displayed' performs a query operation that 'checks if an element is visible on the page' without modifying any state or triggering external actions.
Attacks that exploit this kind of access
checks if an element is visible on the page. It is categorised as a Read tool in the Selenium MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Selenium MCP Server MCP server in PolicyLayer and add a rule for is_element_displayed: 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 Selenium MCP Server. Nothing to install.
is_element_displayed 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 is_element_displayed 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 is_element_displayed. 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.
is_element_displayed is provided by the Selenium MCP Server MCP server (jyothishkumarav/selenium-mcp-server-python). 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 →