create_api
AI agents use create_api to create or update resources in Awslabs Valkey — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Awslabs Valkey environment.
The tool name 'create_api' implies a Write operation (creating a new API resource). However, the description is empty, which significantly lowers confidence. Based on naming convention alone, this is likely a Write action. No evidence of destructive, financial, or execution behavior from the name alone.
From the tool's definition Tool name: 'create_api' — the 'create' prefix suggests creation of a new resource.
Attacks that exploit this kind of access
create_api. It is categorised as a Write tool in the Awslabs Valkey MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Awslabs Valkey 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 Awslabs Valkey. 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 Awslabs Valkey MCP server (awslabs.valkey-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.