Navigate Android TV interface. Requires pairing first (use atv_start_pairing).
AI agents invoke atv_navigate 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.
Navigation of a remote device's interface constitutes executing commands whose effects depend on the navigation path chosen. While not immediately destructive, navigating can trigger secondary effects (launching apps, initiating playback, changing settings). This is Execute rather than Write because it directly manipulates device behavior rather than creating/modifying stored data.
From the tool's definition Tool description states it 'Navigate Android TV interface' and can perform navigation actions on a remote device.
Documented attack patterns abuse exactly the kind of access atv_navigate 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_navigate:
{
"version": "1",
"default": "deny",
"tools": {
"atv_navigate": {
"limits": [
{
"counter": "atv_navigate_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}atv_navigate 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.
Navigate Android TV interface. Requires pairing first (use atv_start_pairing). 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_navigate: 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_navigate 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_navigate 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_navigate. 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_navigate 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.