is_element_visible

Check if a UI element is visible.

SERVERAos SOURCE@hybridlabor-api/aos

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/hybridlabor-api-aos/is-element-visible.md

WHAT IT DOES

What is_element_visible does on Aos

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

RISK

Why is_element_visible is rated Low

Queries visual state of UI elements without modifying data or triggering actions.

From the tool's definition Check if a UI element is visible.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs is_element_visible safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Aos, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For is_element_visible, this is the rule to start with:

is_element_visible Allowed

is_element_visible is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "is_element_visible": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Aos, apply this rule, and every is_element_visible call is checked against it from then on.

FAQ

Questions about is_element_visible

What does the is_element_visible tool do? +

Check if a UI element is visible. It is categorised as a Read tool in the Aos MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on is_element_visible? +

Register the Aos 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 Aos. Nothing to install.

What risk level is is_element_visible? +

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

Can I rate-limit is_element_visible? +

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.

How do I block is_element_visible completely? +

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.

What MCP server provides is_element_visible? +

is_element_visible is provided by the Aos MCP server (@hybridlabor-api/aos). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Aos, and thousands of servers like it.

This server

All 719 Aos tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →