Returns a comprehensive summary of a UI element, including its DOM context, computed styles, and ranked source code candidates. Works with live Chrome selections or stored thread element_context. This is the primary tool to use when the user wants to modify a UI element.
AI agents call get_element_context to retrieve information from Yocoolab without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs data retrieval and analysis only. It inspects UI elements and returns computed information (DOM context, styles, source code candidates) without creating, modifying, deleting, or executing any operations. While it may be used as preparation for modifications (per the description 'primary tool to use when the user wants to modify'), the tool itself is purely informational.
From the tool's definition Returns a comprehensive summary of a UI element, including its DOM context, computed styles, and ranked source code candidates. No modification is described; the tool retrieves and summarizes existing data.
Attacks that exploit this kind of access
Returns a comprehensive summary of a UI element, including its DOM context, computed styles, and ranked source code candidates. Works with live Chrome selections or stored thread element_context. This is the primary tool to use when the user wants to modify a UI element. It is categorised as a Read tool in the Yocoolab MCP Server, which means it retrieves data without modifying state.
Register the Yocoolab MCP server in PolicyLayer and add a rule for get_element_context: 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 Yocoolab. Nothing to install.
get_element_context 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_element_context 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_element_context. 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_element_context is provided by the Yocoolab MCP server (yocoolab/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 →