CreateTokenWithIAM
AI agents call CreateTokenWithIAM as a supporting operation in Amazon ElastiCache Memcached MCP Server workflows.
The description is empty, which significantly lowers confidence. Based on the name alone, 'CreateTokenWithIAM' likely creates an authentication token using IAM credentials for ElastiCache Memcached access. Token creation is a Write operation (creating a new credential/token), but it could also be Read if it's just retrieving/generating a temporary credential.
From the tool's definition Tool name 'CreateTokenWithIAM' and empty description; name suggests token/credential creation via IAM on ElastiCache Memcached context
Attacks that exploit this kind of access
CreateTokenWithIAM. It is categorised as a Other tool in the Amazon ElastiCache Memcached MCP Server MCP Server, which means it performs auxiliary operations.
Register the Amazon ElastiCache Memcached MCP Server MCP server in PolicyLayer and add a rule for CreateTokenWithIAM: 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.
CreateTokenWithIAM is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the CreateTokenWithIAM 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 CreateTokenWithIAM. 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.
CreateTokenWithIAM 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.