create_datasource · Awslabs Valkey MCP: Risk & Policy

WHAT IT DOES

What create_datasource does on Awslabs Valkey

AI agents use create_datasource 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.

WHY IT NEEDS A POLICY

Why create_datasource needs a policy

The 'create_' prefix universally signals data creation, which falls under Write category (reversible modification). While the empty description prevents certainty about the full scope (e.g., whether it could trigger external services), the most straightforward interpretation is that it creates a datasource configuration in ElastiCache/MemoryDB.

From the tool's definition Tool name 'create_datasource' indicates creation of a new data structure or configuration. The empty description limits confidence, but the 'create_' prefix clearly indicates a write operation that adds or modifies data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_datasource Rate-limited

create_datasource stays usable, but capped — an agent stuck in a loop can't make hundreds of changes 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_datasource": {
      "limits": [
        {
          "counter": "create_datasource_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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_datasource

What does the create_datasource tool do? +

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

How do I enforce a policy on create_datasource? +

Register the Awslabs Valkey MCP server in PolicyLayer and add a rule for create_datasource: 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_datasource? +

create_datasource is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_datasource? +

Yes. Add a rate_limit block to the create_datasource 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_datasource completely? +

Set action: deny in the PolicyLayer policy for create_datasource. 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_datasource? +

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