checks if an element is present in the DOM
AI agents call is_element_present 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 only performs a read/query operation to determine DOM element presence. It has no side effects, does not execute code, does not modify data, and does not interact with external systems. It is analogous to other Read category tools on this server like 'find_element' and 'get_element_text' which retrieve page information.
From the tool's definition Tool name 'is_element_present' and description 'checks if an element is present in the DOM' indicate a query operation that retrieves information about page structure without modifying state or triggering actions.
Attacks that exploit this kind of access
checks if an element is present in the DOM. 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_present: 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_present 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_present 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_present. 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_present 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 →