Low Risk

get_all_lights

Get information about all lights connected to the Hue bridge.

How to control get_all_lights ↓

What get_all_lights does on Philips Hue MCP Server

AI agents call get_all_lights to retrieve information from Philips Hue MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_all_lights needs a policy

This tool queries and retrieves data about connected lights without modifying, deleting, or executing any operations. It is a straightforward read operation that returns information only. The blast radius of misuse is minimal—an AI agent could learn about the lighting setup but cannot control, delete, or cause harm through retrieval alone.

From the tool's definition Tool name 'get_all_lights' and description 'Get information about all lights connected to the Hue bridge' indicate a retrieval operation with no side effects.

Documented attack patterns abuse exactly the kind of access get_all_lights gives an agent:

How to control get_all_lights

PolicyLayer is an MCP gateway — it sits between your AI agents and Philips Hue MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_all_lights:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_all_lights": {}
  }
}

get_all_lights is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Philips Hue MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_all_lights

What does the get_all_lights tool do? +

Get information about all lights connected to the Hue bridge. It is categorised as a Read tool in the Philips Hue MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_all_lights? +

Register the Philips Hue MCP Server MCP server in PolicyLayer and add a rule for get_all_lights: 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 Philips Hue MCP Server. Nothing to install.

What risk level is get_all_lights? +

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

Can I rate-limit get_all_lights? +

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

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

get_all_lights is provided by the Philips Hue MCP Server MCP server (thomasrohde/hue-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Philips Hue MCP Server tool call.

Start from Philips Hue MCP Server, 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.

23 Philips Hue MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.