List all scenes available in the account. Token is read from LIFX_API_TOKEN environment variable.
AI agents call list_scenes to retrieve information from LIFX MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves scene metadata from the user's LIFX account without modifying, deleting, or executing any operations. It is a straightforward read operation that queries available scenes. The low severity reflects minimal blast radius—an AI agent misusing this tool would only gain visibility into existing scenes, not control over lights or destructive actions.
From the tool's definition Tool name 'list_scenes' and description 'List all scenes available in the account' indicate a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
List all scenes available in the account. Token is read from LIFX_API_TOKEN environment variable. It is categorised as a Read tool in the LIFX MCP Server MCP Server, which means it retrieves data without modifying state.
Register the LIFX MCP Server MCP server in PolicyLayer and add a rule for list_scenes: 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 LIFX MCP Server. Nothing to install.
list_scenes 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_scenes 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_scenes. 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_scenes is provided by the LIFX MCP Server MCP server (lenvolk/mcp-lifx). 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 →