set_remove · Amazon ElastiCache Memcached MCP Server MCP

WHAT IT DOES

What set_remove does on Amazon ElastiCache Memcached MCP Server

AI agents use set_remove to create or update resources in Amazon ElastiCache Memcached MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Amazon ElastiCache Memcached MCP Server environment.

WHY IT NEEDS A POLICY

Why set_remove needs a policy

The tool modifies data by removing a member from a set, which is a write operation. While removal is technically irreversible in terms of the immediate action, in the context of Memcached it is reversible through re-adding the member, and does not constitute permanent deletion of the underlying cache entry itself.

From the tool's definition Tool name 'set_remove' and description 'Remove member from set' indicate modification of existing data structure by removing an element. This is a reversible write operation (the removed member can be re-added).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_remove Rate-limited

set_remove stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "set_remove": {
      "limits": [
        {
          "counter": "set_remove_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Amazon ElastiCache Memcached MCP Server, so you can run agents against it safely.

FAQ

Questions about set_remove

What does the set_remove tool do? +

Remove member from set. 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 set_remove? +

Register the Amazon ElastiCache Memcached MCP Server MCP server in PolicyLayer and add a rule for set_remove: 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 Amazon ElastiCache Memcached MCP Server. Nothing to install.

What risk level is set_remove? +

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

Can I rate-limit set_remove? +

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

How do I block set_remove completely? +

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

What MCP server provides set_remove? +

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