Run an automated integration test sequence. Orchestrates multiple actions in order: deploy, wait, screenshot, keypress, check_log, sg_nodes, element, perf, media_player, check_resolution, server_check, deep_link, check_drm, check_raf, check_accessibility. Each step result is collected into a test...
AI agents invoke roku_run_test 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 executes an automated test sequence that performs multiple external operations on a Roku device, including deployment, input simulation (keypress), and triggering various device functions. While individual steps may appear benign (screenshot, check_log), the orchestration of execute-class operations (deploy, keypress, deep_link) that trigger device state changes classifies this as Execute.
From the tool's definition Tool name 'roku_run_test' and description states it 'Orchestrates multiple actions in order: deploy, wait, screenshot, keypress, check_log, sg_nodes, element, perf, media_player, check_resolution, server_check, deep_link, check_drm, check_raf,…
Attacks that exploit this kind of access
Run an automated integration test sequence. Orchestrates multiple actions in order: deploy, wait, screenshot, keypress, check_log, sg_nodes, element, perf, media_player, check_resolution, server_check, deep_link, check_drm, check_raf, check_accessibility. Each step result is collected into a test report with pass/fail status. Screenshots are captured as base64 images. Example steps: [{. 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_run_test: 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_run_test 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_run_test 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_run_test. 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_run_test 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 →