Add a new TV device with specified IP address and port.
AI agents use add_tv_device to create or update resources in Smart Home Control MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Smart Home Control MCP Server environment.
This tool creates a new TV device entry in the smart home system configuration, which is a reversible write operation. While it modifies persistent state (adds a device to the system), the action can be undone by removing the device.
From the tool's definition Tool name is 'add_tv_device' and description states 'Add a new TV device with specified IP address and port' — the verb 'add' indicates creation of new configuration data.
Attacks that exploit this kind of access
Add a new TV device with specified IP address and port. It is categorised as a Write tool in the Smart Home Control MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Smart Home Control MCP Server MCP server in PolicyLayer and add a rule for add_tv_device: 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 Smart Home Control MCP Server. Nothing to install.
add_tv_device 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 add_tv_device 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 add_tv_device. 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.
add_tv_device is provided by the Smart Home Control MCP Server MCP server (surya443/smart-home-mcp-server). 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 →