AI agents call is_element_visible to retrieve information from MacWright without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves and reports the visibility state of a DOM element in Safari. It performs no modifications, executions, deletions, or financial operations. The return values are used for conditional logic, confirming its nature as a pure read operation with no side effects.
From the tool's definition Tool description states it 'Check[s] whether a DOM element exists AND is visible' and 'Returns {exists, visible, inViewport}' — purely a query operation that returns visibility status without modifying state or triggering actions.
Attacks that exploit this kind of access
Check whether a DOM element exists AND is visible in the current Safari viewport. Returns {exists, visible, inViewport} — useful for conditional logic without waiting. It is categorised as a Read tool in the MacWright MCP Server, which means it retrieves data without modifying state.
Register the MacWright MCP server in PolicyLayer and add a rule for is_element_visible: 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 MacWright. Nothing to install.
is_element_visible 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_visible 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_visible. 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_visible is provided by the MacWright MCP server (ruchit-p/macwright). 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 →