db.start_connection · MCP Fullstack MCP: Risk & Policy

WHAT IT DOES

What db.start_connection does on MCP Fullstack

AI agents invoke db.start_connection to trigger actions in MCP Fullstack. 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 db.start_connection needs a policy

This tool establishes a database connection, which is an operation that triggers external system interaction and enables execution of arbitrary database commands. While the connection itself is not destructive, it is a gateway to Execute-category operations (db.end_connection, queries, etc.).

From the tool's definition "Start a new database connection" - initiates a database connection which enables subsequent database operations whose effects depend on how the connection is used (queries, modifications, or deletions).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

db.start_connection Rate-limited

db.start_connection 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": {
    "db.start_connection": {
      "limits": [
        {
          "counter": "db.start_connection_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 MCP Fullstack, so you can run agents against it safely.

FAQ

Questions about db.start_connection

What does the db.start_connection tool do? +

Start a new database connection. It is categorised as a Execute tool in the MCP Fullstack MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on db.start_connection? +

Register the MCP Fullstack MCP server in PolicyLayer and add a rule for db.start_connection: 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 MCP Fullstack. Nothing to install.

What risk level is db.start_connection? +

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

Can I rate-limit db.start_connection? +

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

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

db.start_connection is provided by the MCP Fullstack MCP server (jacobfv/mcp-fullstack). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.