This record as markdown: /tools/tolpo/set-light.md
What set_light does on Tolpo
AI agents use set_light to create or update resources in Tolpo, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tolpo environment.
Why set_light is rated Medium
The tool modifies lighting device state (on/off, brightness, color, etc.), which is reversible and non-destructive. This constitutes Write rather than Execute because it targets a specific resource state change rather than running arbitrary code. Severity is medium: misuse could disrupt occupant comfort or smart home routines, but has no financial, destructive, or safety-critical consequences in typical scenarios.
From the tool's definition Tool name 'set_light' combined with sibling tools 'set_group' and context of 'control of Philips Hue lighting devices' indicates modification of light state. Description is empty, requiring inference from name and server context.
Attacks that exploit this kind of access
The rule that runs set_light safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Tolpo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For set_light, this is the rule to start with:
set_light stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Tolpo, apply this rule, and every set_light call is checked against it from then on.
Questions about set_light
set_light is a write tool on the Tolpo MCP server. It is categorised as a Write tool in the Tolpo MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Tolpo MCP server in PolicyLayer and add a rule for set_light: 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 Tolpo. Nothing to install.
set_light is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the set_light 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 set_light. 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.
set_light is provided by the Tolpo MCP server (signerless/tolpo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Tolpo, and thousands of servers like it.
This server
Across the catalogue