AI agents call get_element_info to retrieve information from InSite without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries DOM element information (properties, attributes, computed styles, etc.) without causing side effects, data modification, or destructive changes. It is a read-only introspection operation. While it runs JavaScript, the JavaScript is scoped to querying element state rather than executing arbitrary user commands or triggering external operations.
From the tool's definition Tool name 'get_element_info' and description 'Get comprehensive information about an element using JavaScript' indicate retrieval of element properties and metadata without modification, deletion, or execution of arbitrary code.
Attacks that exploit this kind of access
Get comprehensive information about an element using JavaScript. It is categorised as a Read tool in the InSite MCP Server, which means it retrieves data without modifying state.
Register the InSite MCP server in PolicyLayer and add a rule for get_element_info: 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 InSite. Nothing to install.
get_element_info 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_info 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_info. 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_info is provided by the InSite MCP server (jowharshamshiri/insite). 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 →