Find positions of bits set to a specific value. Args: key: The name of the bitmap key bit: Bit value to search for (0 or 1) start: Start offset (inclusive, optional) end: End offset (inclusive, optional) count: Maximum number of positions to return (optional) Returns: Li...
Single-target operation
Part of the Awslabs Valkey MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents invoke bitmap_pos to trigger processes or run actions in Awslabs Valkey. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
bitmap_pos can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
tools:
bitmap_pos:
rules:
- action: allow
rate_limit:
max: 10
window: 60
validate:
required_args: trueSee the full Awslabs Valkey policy for all 105 tools.
Agents calling execute-class tools like bitmap_pos have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
bitmap_pos is one of the high-risk operations in Awslabs Valkey. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.
Find positions of bits set to a specific value. Args: key: The name of the bitmap key bit: Bit value to search for (0 or 1) start: Start offset (inclusive, optional) end: End offset (inclusive, optional) count: Maximum number of positions to return (optional) Returns: List of positions or error message. It is categorised as a Execute tool in the Awslabs Valkey MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Add a rule in your Intercept YAML policy under the tools section for bitmap_pos. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Awslabs Valkey MCP server.
bitmap_pos is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the bitmap_pos 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 bitmap_pos. 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.
bitmap_pos 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.