create_resolver | PolicyLayer

WHAT IT DOES

What create_resolver does on Amazon ElastiCache Memcached MCP Server

AI agents use create_resolver 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 create_resolver needs a policy

The tool name indicates a create operation, which is reversible (Write category) rather than destructive. The empty description reduces confidence, but the ElastiCache context and 'create' verb suggest this modifies configuration by adding a new resolver. Severity is medium because resolver misconfiguration could impact availability or routing, but the effect is reversible via deletion or modification.

From the tool's definition Tool name 'create_resolver' on ElastiCache Memcached MCP server. Description is empty; classification inferred from context (AWS ElastiCache service) and naming pattern suggesting creation of a resolver resource (likely DNS or endpoint resolver).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_resolver Rate-limited

create_resolver 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": {
    "create_resolver": {
      "limits": [
        {
          "counter": "create_resolver_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 create_resolver

What does the create_resolver tool do? +

create_resolver. 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 create_resolver? +

Register the Amazon ElastiCache Memcached MCP Server MCP server in PolicyLayer and add a rule for create_resolver: 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 create_resolver? +

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

Can I rate-limit create_resolver? +

Yes. Add a rate_limit block to the create_resolver 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 create_resolver completely? +

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

create_resolver 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.