create_agent_runtime_endpoint · Awslabs Valkey MCP

WHAT IT DOES

What create_agent_runtime_endpoint does on Awslabs Valkey

AI agents invoke create_agent_runtime_endpoint to trigger actions in Awslabs Valkey. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why create_agent_runtime_endpoint needs a policy

The name suggests creating a runtime endpoint for an agent, which implies provisioning/deploying infrastructure or activating a service endpoint. This could be a Write (creating a resource) but given it involves a 'runtime' and 'endpoint' activation, it likely spans into Execute territory (triggering external operations). With no description available, confidence is reduced.

From the tool's definition Tool name: create_agent_runtime_endpoint — description is empty and uninformative.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_agent_runtime_endpoint Rate-limited

create_agent_runtime_endpoint stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_agent_runtime_endpoint": {
      "limits": [
        {
          "counter": "create_agent_runtime_endpoint_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Awslabs Valkey, so you can run agents against it safely.

FAQ

Questions about create_agent_runtime_endpoint

What does the create_agent_runtime_endpoint tool do? +

create_agent_runtime_endpoint. It is categorised as a Execute tool in the Awslabs Valkey MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on create_agent_runtime_endpoint? +

Register the Awslabs Valkey MCP server in PolicyLayer and add a rule for create_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.

What risk level is create_agent_runtime_endpoint? +

create_agent_runtime_endpoint is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit create_agent_runtime_endpoint? +

Yes. Add a rate_limit block to the create_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.

How do I block create_agent_runtime_endpoint completely? +

Set action: deny in the PolicyLayer policy for create_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.

What MCP server provides create_agent_runtime_endpoint? +

create_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.