Remove occurrences of value from list. Args: key: The name of the key value: Value to remove count: Number of occurrences to remove (0 for all, positive for left-to-right, negative for right-to-left) Returns: Success message or error message
Part of the Awslabs Valkey MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call list_remove to retrieve information from Awslabs Valkey without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though list_remove only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
list_remove:
rules:
- action: allowSee the full Awslabs Valkey policy for all 105 tools.
Agents calling read-class tools like list_remove have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Remove occurrences of value from list. Args: key: The name of the key value: Value to remove count: Number of occurrences to remove (0 for all, positive for left-to-right, negative for right-to-left) Returns: Success message or error message. It is categorised as a Read tool in the Awslabs Valkey MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for list_remove. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Awslabs Valkey MCP server.
list_remove 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_remove rule in your Intercept 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 Intercept policy for list_remove. 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_remove is provided by the Awslabs Valkey MCP server (awslabs.valkey-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.