create_api
AI agents use create_api 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 tool name 'create_api' suggests it creates or provisions an API resource, which is a Write operation that creates data/infrastructure reversibly. Without a description, confidence is moderate. The severity is medium because creating APIs could enable unwanted external access or integrations, but the impact depends on what permissions and configurations are applied. The empty description reduces confidence to 0.6.
From the tool's definition Tool name is 'create_api' which indicates creation of an API resource. Description is empty, providing no additional context.
Attacks that exploit this kind of access
create_api. 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 create_api: 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.
create_api 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 create_api 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 create_api. 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.
create_api 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.