Medium Risk

connect_to_database

Connect to a specific database and save the connection internally

Single-target operation

Part of the AWS Labs postgres MCP Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents use connect_to_database to create or modify resources in AWS Labs postgres MCP Server. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call connect_to_database repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach AWS Labs postgres MCP Server.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

aws-labs-postgres-mcp-server.yaml
tools:
  connect_to_database:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full AWS Labs postgres MCP Server policy for all 7 tools.

Tool Name connect_to_database
Category Write
Risk Level Medium

Agents calling write-class tools like connect_to_database have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

What does the connect_to_database tool do? +

Connect to a specific database and save the connection internally. It is categorised as a Write tool in the AWS Labs postgres MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on connect_to_database? +

Add a rule in your Intercept YAML policy under the tools section for connect_to_database. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the AWS Labs postgres MCP Server MCP server.

What risk level is connect_to_database? +

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

Can I rate-limit connect_to_database? +

Yes. Add a rate_limit block to the connect_to_database rule in your Intercept 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 Intercept 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 AWS Labs postgres MCP Server MCP server (awslabs.postgres-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.