get_element_at_position

Get the DOM element at a specific screen position. Args: x: X coordinate y: Y coordinate Returns: Node information at the specified position

SERVERChrome Devtools SOURCEbenjaminr/chrome-devtools-mcp
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/benjaminr-chrome-devtools-mcp/get-element-at-position.md

What get_element_at_position does on Chrome Devtools

AI agents call get_element_at_position to retrieve information from Chrome Devtools without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_element_at_position is rated Low

This tool queries and retrieves DOM node information based on screen coordinates. It performs a read-only inspection of the page structure without creating, modifying, deleting, or executing any code.

From the tool's definition Tool name 'get_element_at_position' and description state it 'Get[s] the DOM element at a specific screen position' and 'Returns: Node information at the specified position'. These are retrieval operations with no modification of state.

Questions about get_element_at_position

What does the get_element_at_position tool do? +

Get the DOM element at a specific screen position. Args: x: X coordinate y: Y coordinate Returns: Node information at the specified position. It is categorised as a Read tool in the Chrome Devtools MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_element_at_position? +

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

What risk level is get_element_at_position? +

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

Can I rate-limit get_element_at_position? +

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

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

get_element_at_position is provided by the Chrome Devtools MCP server (benjaminr/chrome-devtools-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Chrome Devtools, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Chrome Devtools's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.