AI agents invoke atv_complete_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.
This tool completes a pairing process with an Android TV device using a PIN code, establishing a persistent authenticated connection. It triggers an external operation (device pairing) with lasting effects (the device becomes paired/trusted), making it Execute. Misuse could allow an AI to pair with devices without user intent, but it doesn't delete data or move money.
From the tool's definition Complete pairing process with PIN code
Documented attack patterns abuse exactly the kind of access atv_complete_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_complete_pairing:
{
"version": "1",
"default": "deny",
"tools": {
"atv_complete_pairing": {
"limits": [
{
"counter": "atv_complete_pairing_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}atv_complete_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.
Complete pairing process with PIN code. 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_complete_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_complete_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_complete_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_complete_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_complete_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.