list_agent_runtimes
AI agents call list_agent_runtimes to retrieve information from Awslabs Valkey without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name suggests it retrieves a list of available agent runtimes. Despite the empty description limiting confidence, the 'list' prefix strongly indicates a read operation that queries configuration or status data. No modification, deletion, or execution capabilities are implied. Confidence is reduced due to lack of descriptive detail, but the category is clear.
From the tool's definition Tool name 'list_agent_runtimes' uses the verb 'list', which by convention retrieves or queries data without side effects.
Attacks that exploit this kind of access
list_agent_runtimes. It is categorised as a Read tool in the Awslabs Valkey MCP Server, which means it retrieves data without modifying state.
Register the Awslabs Valkey MCP server in PolicyLayer and add a rule for list_agent_runtimes: 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 Awslabs Valkey. Nothing to install.
list_agent_runtimes 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 list_agent_runtimes 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 list_agent_runtimes. 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.
list_agent_runtimes is provided by the Awslabs Valkey MCP server (awslabs.valkey-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.