delete_agent_runtime_endpoint
AI agents call delete_agent_runtime_endpoint to permanently remove resources in Awslabs Valkey — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The 'delete_' prefix conventionally indicates destructive operations that cannot be undone. Deleting an agent runtime endpoint would remove infrastructure and potentially disrupt dependent services. This is categorized as Destructive rather than Write because deletion is irreversible. Confidence is lowered from 0.95 to 0.85 due to the empty description, though the intent is clear from nomenclature.
From the tool's definition Tool name contains 'delete' which indicates irreversible removal of a resource (agent runtime endpoint). The tool description is empty, preventing confirmation of exact behavior, but the naming convention strongly suggests permanent deletion of AWS…
Documented attack patterns abuse exactly the kind of access delete_agent_runtime_endpoint gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Awslabs Valkey, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_agent_runtime_endpoint:
{
"version": "1",
"default": "deny",
"hide": [
"delete_agent_runtime_endpoint"
]
}delete_agent_runtime_endpoint disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
delete_agent_runtime_endpoint. It is categorised as a Destructive tool in the Awslabs Valkey MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Awslabs Valkey MCP server in PolicyLayer and add a rule for delete_agent_runtime_endpoint: 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.
delete_agent_runtime_endpoint is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_agent_runtime_endpoint 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 delete_agent_runtime_endpoint. 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.
delete_agent_runtime_endpoint 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.
Start from Awslabs Valkey, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
805 Awslabs Valkey tools catalogued and risk-classified — across an index of 43,000+ MCP servers.