AI agents call alexa_list_routines to retrieve information from Alexa without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves configuration data about existing Alexa routines without creating, modifying, deleting, or executing them. It has no side effects and poses minimal security risk; an adversary gaining access could learn about automation workflows but cannot manipulate them directly. Severity is low because the blast radius is limited to information disclosure.
From the tool's definition Tool 'lists' Alexa routines and 'shows' routine names, triggers, and actions—purely informational retrieval with no modification, deletion, or execution of routines.
Attacks that exploit this kind of access
List all Alexa routines configured in the account. Shows routine names, triggers, and actions. It is categorised as a Read tool in the Alexa MCP Server, which means it retrieves data without modifying state.
Register the Alexa MCP server in PolicyLayer and add a rule for alexa_list_routines: 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 Alexa. Nothing to install.
alexa_list_routines 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 alexa_list_routines 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 alexa_list_routines. 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.
alexa_list_routines is provided by the Alexa MCP server (serversmx/alexa-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 →