Send a remote control key press to the Roku device. Roku API: POST http://{host}:8060/keypress/{key} Available keys: Home, Rev, Fwd, Play, Select, Left, Right, Down, Up, Back, InstantReplay, Info, Backspace, Search, Enter, VolumeDown, VolumeMute, VolumeUp, PowerOff, ChannelUp, ChannelDown, Lit_{c...
AI agents invoke roku_keypress to trigger actions in Roku MCP Server. 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 sends key press commands to an external Roku device via HTTP POST, triggering real device actions (navigation, text input, power control, volume changes). It executes external operations on a physical device. The PowerOff key could be disruptive, but overall the blast radius is medium since misuse is limited to controlling a single Roku device rather than affecting data or financial systems.
From the tool's definition Send a remote control key press to the Roku device. POST http://{host}:8060/keypress/{key}
Attacks that exploit this kind of access
Send a remote control key press to the Roku device. Roku API: POST http://{host}:8060/keypress/{key} Available keys: Home, Rev, Fwd, Play, Select, Left, Right, Down, Up, Back, InstantReplay, Info, Backspace, Search, Enter, VolumeDown, VolumeMute, VolumeUp, PowerOff, ChannelUp, ChannelDown, Lit_{character} (for text input, e.g., Lit_a, Lit_1) Ref: developer.roku.com/docs/developer-program/debugging/external-control-api.md. It is categorised as a Execute tool in the Roku MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Roku MCP Server MCP server in PolicyLayer and add a rule for roku_keypress: 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 Roku MCP Server. Nothing to install.
roku_keypress 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 roku_keypress 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 roku_keypress. 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.
roku_keypress is provided by the Roku MCP Server MCP server (maskelog/roku-mcp). 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 →