Get the current state of a Switcher device
AI agents call get_device_state to retrieve information from Switcher MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries device state information without side effects or modifications. It is a retrieval operation that poses minimal security risk even if misused by an AI agent, as it only returns status data about a Switcher KIS device. No data is created, modified, deleted, or financial transactions are involved.
From the tool's definition Tool description explicitly states 'Get the current state' with no mention of modifications, and the function name 'get_device_state' follows read-only naming conventions (get/retrieve pattern).
Attacks that exploit this kind of access
Get the current state of a Switcher device. It is categorised as a Read tool in the Switcher MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Switcher MCP Server MCP server in PolicyLayer and add a rule for get_device_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 Switcher MCP Server. Nothing to install.
get_device_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_device_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_device_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_device_state is provided by the Switcher MCP Server MCP server (liebstein/switcher-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 →