Set the TV input source (e.g., hdmi1) via SmartThings
AI agents use tv_set_input to create or update resources in MCP Server Template — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Server Template environment.
This tool modifies device configuration by changing the input source, which is a reversible write operation. It does not execute arbitrary code, delete data, or transfer funds. Severity is medium because misuse could disrupt user experience or cause unwanted device state changes, but the action is recoverable (user can switch input back).
From the tool's definition Tool name 'tv_set_input' and description 'Set the TV input source' indicate modifying TV state; sibling tools (tv_turn_on, tv_turn_off, tv_set_volume) confirm this server controls physical device settings via SmartThings API.
Attacks that exploit this kind of access
Set the TV input source (e.g., hdmi1) via SmartThings. It is categorised as a Write tool in the MCP Server Template MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Server Template MCP server in PolicyLayer and add a rule for tv_set_input: 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 MCP Server Template. Nothing to install.
tv_set_input 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 tv_set_input 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 tv_set_input. 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.
tv_set_input is provided by the MCP Server Template MCP server (kj14god/tvmcp). 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 →