Launch or restart an app on the Roku device. Roku API: POST http://{host}:8060/launch/{appId}?{params} Use appId=
AI agents invoke roku_launch 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.
Launching/restarting applications is an Execute action—it runs code/operations on an external device whose effects depend on arguments and cannot be purely read-only. While not destructive, write-based, or financial, it actively triggers side effects on the target device.
From the tool's definition Tool 'roku_launch' performs POST action to '/launch/{appId}' endpoint, which triggers execution of an application on a Roku device.
Attacks that exploit this kind of access
Launch or restart an app on the Roku device. Roku API: POST http://{host}:8060/launch/{appId}?{params} Use appId=. 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_launch: 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_launch 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_launch 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_launch. 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_launch 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 →