Read app registry (stored settings/data). Roku API: GET http://{host}:8060/query/registry/{appId} Returns: sections and key-value pairs stored in the device registry. Use appId=
AI agents call roku_registry to retrieve information from Roku MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves stored settings and configuration data from the Roku device registry without altering or deleting anything. It is a pure read operation with no side effects. The GET request and explicit 'Read' designation in the description confirm it belongs in the Read category.
From the tool's definition Tool name includes 'Read' prefix; description states 'Read app registry'; HTTP method is GET (read-only); returns 'sections and key-value pairs' without modification.
Attacks that exploit this kind of access
Read app registry (stored settings/data). Roku API: GET http://{host}:8060/query/registry/{appId} Returns: sections and key-value pairs stored in the device registry. Use appId=. It is categorised as a Read tool in the Roku MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Roku MCP Server MCP server in PolicyLayer and add a rule for roku_registry: 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_registry is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the roku_registry 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_registry. 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_registry 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 →