list_app_schedules
AI agents call list_app_schedules 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 'list' prefix strongly implies a read-only query operation that retrieves and displays application schedules without side effects. While the empty description reduces confidence slightly, the semantic meaning of 'list' as a retrieval verb is clear and consistent with Read category tools like 'list' and 'get' operations.
From the tool's definition Tool name 'list_app_schedules' indicates a retrieval operation (list). No description provided, but naming convention suggests querying or enumerating schedule data without modification.
Attacks that exploit this kind of access
list_app_schedules. 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_app_schedules: 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_app_schedules 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_app_schedules 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_app_schedules. 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_app_schedules 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.