Medium Risk

cache_cas

Set a value using CAS (Check And Set). Args: key: The key to set value: The value to store cas: CAS token from gets() expire: Optional expiration time in seconds Returns: Success message or error message

Part of the Amazon ElastiCache Memcached MCP Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents use cache_cas to create or modify resources in Amazon ElastiCache Memcached MCP Server. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call cache_cas repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Amazon ElastiCache Memcached MCP Server.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

amazon-elasticache-memcached-mcp-server.yaml
tools:
  cache_cas:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Amazon ElastiCache Memcached MCP Server policy for all 22 tools.

Tool Name cache_cas
Category Write
Risk Level Medium

View all 22 tools →

Agents calling write-class tools like cache_cas have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

What does the cache_cas tool do? +

Set a value using CAS (Check And Set). Args: key: The key to set value: The value to store cas: CAS token from gets() expire: Optional expiration time in seconds Returns: Success message or error message. It is categorised as a Write tool in the Amazon ElastiCache Memcached MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on cache_cas? +

Add a rule in your Intercept YAML policy under the tools section for cache_cas. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Amazon ElastiCache Memcached MCP Server MCP server.

What risk level is cache_cas? +

cache_cas is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit cache_cas? +

Yes. Add a rate_limit block to the cache_cas 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.

How do I block cache_cas completely? +

Set action: deny in the Intercept policy for cache_cas. 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.

What MCP server provides cache_cas? +

cache_cas is provided by the Amazon ElastiCache Memcached MCP Server MCP server (awslabs.memcached-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.