AI agents use set_locator_led to create or update resources in Cimc — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Cimc environment.
This tool creates or modifies a physical hardware state (locator LED state) reversibly. It does not read-only, does not execute code or commands, does not permanently destroy data, and has no financial implications. The impact is limited to a visual indicator used for physical identification. Misuse would result in temporarily incorrect LED state, which is easily corrected.
From the tool's definition The tool 'set_locator_led' modifies the state of a physical LED on the server (on or off), which is a reversible change to server state.
Attacks that exploit this kind of access
Turn the server locator LED on or off. Used to physically identify a server in a rack. It is categorised as a Write tool in the Cimc MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Cimc MCP server in PolicyLayer and add a rule for set_locator_led: 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 Cimc. Nothing to install.
set_locator_led 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_locator_led 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_locator_led. 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_locator_led is provided by the Cimc MCP server (schwarztim/cimc-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 →