Check if TV is connected and available.
AI agents call check_tv_connection to retrieve information from Smart Home Control 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 status check operation with no side effects. It retrieves information about device connectivity without creating, modifying, deleting, or executing anything on the device. This is a straightforward Read category action with low severity as misuse would only expose connectivity information.
From the tool's definition Tool name 'check_tv_connection' and description 'Check if TV is connected and available' indicate a read-only operation that queries the connection status without modifying device state or triggering actions.
Attacks that exploit this kind of access
Check if TV is connected and available. It is categorised as a Read tool in the Smart Home Control MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Smart Home Control MCP Server MCP server in PolicyLayer and add a rule for check_tv_connection: 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.
check_tv_connection 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 check_tv_connection 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 check_tv_connection. 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.
check_tv_connection 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 →