connect_to_database · Awslabs Valkey MCP: Risk & Policy

WHAT IT DOES

What connect_to_database does on Awslabs Valkey

AI agents invoke connect_to_database 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 connect_to_database needs a policy

This tool establishes a live database connection to a SQL Server RDS instance and persists that connection internally. It triggers an external operation (network connection to a remote database) with side effects (saved internal state). Misuse could expose sensitive database credentials or grant an AI agent persistent access to a production database, making severity high.

From the tool's definition Connect to a SQL Server RDS instance and save the connection internally

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

connect_to_database Rate-limited

connect_to_database 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": {
    "connect_to_database": {
      "limits": [
        {
          "counter": "connect_to_database_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 connect_to_database

What does the connect_to_database tool do? +

Connect to a SQL Server RDS instance and save the connection internally. 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 connect_to_database? +

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

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

Can I rate-limit connect_to_database? +

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

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

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