List all available Heroicons for use with flux:icon component, with variants and usage examples
AI agents call list_flux_component_icons to retrieve information from Livewire Flux without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and lists documentation about available icons and their variants with no side effects. It performs a read-only query of available resources without modifying, deleting, or executing any external operations. The minimal blast radius of misuse (providing incorrect icon lists or documentation) makes this a low-severity Read category tool.
From the tool's definition Tool name 'list_flux_component_icons' and description 'List all available Heroicons' indicate a retrieval operation that provides information about available icons and their variants.
Documented attack patterns abuse exactly the kind of access list_flux_component_icons gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Livewire Flux, and nothing reaches the server without passing your rules. This is the rule we recommend for list_flux_component_icons:
{
"version": "1",
"default": "deny",
"tools": {
"list_flux_component_icons": {}
}
}list_flux_component_icons is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all available Heroicons for use with flux:icon component, with variants and usage examples. It is categorised as a Read tool in the Livewire Flux MCP Server, which means it retrieves data without modifying state.
Register the Livewire Flux MCP server in PolicyLayer and add a rule for list_flux_component_icons: 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 Livewire Flux. Nothing to install.
list_flux_component_icons 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 list_flux_component_icons 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 list_flux_component_icons. 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.
list_flux_component_icons is provided by the Livewire Flux MCP server (lemaur/livewire-flux-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Livewire Flux, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
4 Livewire Flux tools catalogued and risk-classified — across an index of 43,000+ MCP servers.