Start pairing process with an Android TV device
AI agents invoke atv_start_pairing to trigger actions in AndroidTVMCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Pairing is an execute-class operation because it triggers an external device operation whose effects depend on which device is targeted. While not immediately destructive or financial, it establishes remote control capabilities over hardware and could enable subsequent malicious actions (captured in sibling tools like atv_launch_app, atv_cast_url, atv_input_text).
From the tool's definition Tool description states 'Start pairing process with an Android TV device' — this initiates a security-relevant pairing handshake that establishes a persistent trust relationship and control channel with a physical device.
Documented attack patterns abuse exactly the kind of access atv_start_pairing gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and AndroidTVMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for atv_start_pairing:
{
"version": "1",
"default": "deny",
"tools": {
"atv_start_pairing": {
"limits": [
{
"counter": "atv_start_pairing_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}atv_start_pairing stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Start pairing process with an Android TV device. It is categorised as a Execute tool in the AndroidTVMCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the AndroidTV MCP server in PolicyLayer and add a rule for atv_start_pairing: 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 AndroidTVMCP. Nothing to install.
atv_start_pairing is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the atv_start_pairing 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 atv_start_pairing. 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.
atv_start_pairing is provided by the AndroidTV MCP server (pigeek/androidtvmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from AndroidTVMCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
17 AndroidTVMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.