bosch_camera_light_set
AI agents use bosch_camera_light_set to create or update resources in Bosch Smart Home Camera MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Bosch Smart Home Camera MCP Server environment.
The tool name suggests it sets or changes the light configuration on a Bosch Smart Home Camera (e.g., toggling an indicator light or infrared illumination). This is a reversible state change, placing it in the Write category. Confidence is lowered due to the empty description.
From the tool's definition Tool name 'bosch_camera_light_set' — 'set' implies a write/configuration change; description is empty providing no further detail.
Attacks that exploit this kind of access
bosch_camera_light_set. It is categorised as a Write tool in the Bosch Smart Home Camera MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Bosch Smart Home Camera MCP Server MCP server in PolicyLayer and add a rule for bosch_camera_light_set: 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 Bosch Smart Home Camera MCP Server. Nothing to install.
bosch_camera_light_set 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 bosch_camera_light_set 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 bosch_camera_light_set. 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.
bosch_camera_light_set is provided by the Bosch Smart Home Camera MCP Server MCP server (mosandlt/bosch-smart-home-camera-tool-mcp). 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 →