gateway_create
AI agents use gateway_create 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.
The 'create' verb combined with 'gateway' context suggests this tool provisions or initializes a new ElastiCache gateway resource. This is reversible (can be deleted) and has side effects limited to resource creation, placing it in Write rather than Execute or Destructive.
From the tool's definition Tool name 'gateway_create' indicates creation of a resource (gateway). The empty description limits precision, but 'create' operations are typically Write-category actions that modify infrastructure state.
Attacks that exploit this kind of access
gateway_create. 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.
Register the Amazon ElastiCache Memcached MCP Server MCP server in PolicyLayer and add a rule for gateway_create: 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.
gateway_create is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the gateway_create 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.
Set action: deny in the PolicyLayer policy for gateway_create. 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.
gateway_create 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.