Return the last-known power state for one device (Redfish/IPMI/PDU-backed). Read-only.
AI agents call get_power_state to retrieve information from KVMFleet MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a simple read operation to retrieve the power state of a KVM Fleet device. It queries existing data without modification, deletion, or execution of commands. The blast radius of misuse is minimal — an attacker gains only visibility into device power states, which does not enable further compromise without additional tools.
From the tool's definition Tool description explicitly states 'Read-only' and the operation is 'Return the last-known power state' — a query operation with no side effects that retrieves device status information.
Attacks that exploit this kind of access
Return the last-known power state for one device (Redfish/IPMI/PDU-backed). Read-only. It is categorised as a Read tool in the KVMFleet MCP Server MCP Server, which means it retrieves data without modifying state.
Register the KVMFleet MCP Server MCP server in PolicyLayer and add a rule for get_power_state: 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 KVMFleet MCP Server. Nothing to install.
get_power_state 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 get_power_state 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 get_power_state. 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.
get_power_state is provided by the KVMFleet MCP Server MCP server (kvmfleet/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 →