This record as markdown: /tools/hybridlabor-api-aos/highlight-element.md
What highlight_element does on Aos
AI agents invoke highlight_element to trigger actions in Aos. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why highlight_element is rated High
Based on the server context (browser automation/visual annotation) and sibling tools that perform browser interactions, 'highlight_element' likely draws a visual highlight or annotation on a page element — an Execute-level browser action. Confidence is reduced due to empty description; it could also be purely Read/visual. Most severe plausible interpretation given context is Execute.
From the tool's definition Tool name 'highlight_element' on a server that performs browser actions (click, annotate, screenshot). Description is empty/uninformative.
Attacks that exploit this kind of access
The rule that runs highlight_element 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 highlight_element, this is the rule to start with:
highlight_element stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Aos, apply this rule, and every highlight_element call is checked against it from then on.
Questions about highlight_element
highlight_element is a execute tool on the Aos MCP server. It is categorised as a Execute tool in the Aos MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Aos MCP server in PolicyLayer and add a rule for highlight_element: 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.
highlight_element is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the highlight_element 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 highlight_element. 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.
highlight_element 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.
More on Aos, and thousands of servers like it.
This server
Across the catalogue