New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

libi.highlight_property

Guided edit: flash a specific inspector field for an overlay so the user sees exactly which control to change. Pass the overlay id and a known property key (e.g.

SERVERLibi SOURCENagellabs/libi
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/libi/libi.highlight-property.md

What libi.highlight_property does on Libi

AI agents invoke libi.highlight_property to trigger actions in Libi. 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 libi.highlight_property is rated High

Triggers a UI action (flashing/highlighting) that affects the application's visual state.

From the tool's definition flash a specific inspector field... so the user sees exactly which control

Questions about libi.highlight_property

What does the libi.highlight_property tool do? +

Guided edit: flash a specific inspector field for an overlay so the user sees exactly which control to change. Pass the overlay id and a known property key (e.g. It is categorised as a Execute tool in the Libi MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on libi.highlight_property? +

Register the Libi MCP server in PolicyLayer and add a rule for libi.highlight_property: 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 Libi. Nothing to install.

What risk level is libi.highlight_property? +

libi.highlight_property is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit libi.highlight_property? +

Yes. Add a rate_limit block to the libi.highlight_property 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 libi.highlight_property completely? +

Set action: deny in the PolicyLayer policy for libi.highlight_property. 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 libi.highlight_property? +

libi.highlight_property is provided by the Libi MCP server (Nagellabs/libi). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Libi, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Libi's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.