Critical Risk →

atv_unpair_device

Unpair an Android TV device

How to control atv_unpair_device ↓

What atv_unpair_device does on AndroidTVMCP

AI agents call atv_unpair_device to permanently remove resources in AndroidTVMCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why atv_unpair_device needs a policy

Unpairing a device destroys the established trust/authentication relationship. This cannot be undone automatically; the user must go through the pairing process again. It could lock the AI assistant out of device control entirely, making it a destructive operation with high blast radius if misused.

From the tool's definition 'Unpair an Android TV device' — removing a pairing is an irreversible action that severs the connection between the AI assistant and the device, requiring re-pairing to restore control.

Documented attack patterns abuse exactly the kind of access atv_unpair_device gives an agent:

How to control atv_unpair_device

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_unpair_device:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "atv_unpair_device"
  ]
}

atv_unpair_device disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register AndroidTVMCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about atv_unpair_device

What does the atv_unpair_device tool do? +

Unpair an Android TV device. It is categorised as a Destructive tool in the AndroidTVMCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on atv_unpair_device? +

Register the AndroidTV MCP server in PolicyLayer and add a rule for atv_unpair_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 AndroidTVMCP. Nothing to install.

What risk level is atv_unpair_device? +

atv_unpair_device is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit atv_unpair_device? +

Yes. Add a rate_limit block to the atv_unpair_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.

How do I block atv_unpair_device completely? +

Set action: deny in the PolicyLayer policy for atv_unpair_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.

What MCP server provides atv_unpair_device? +

atv_unpair_device 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.

Enforce policy on every AndroidTVMCP tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.