db.end_connection · MCP Fullstack MCP: Risk & Policy

WHAT IT DOES

What db.end_connection does on MCP Fullstack

AI agents use db.end_connection to create or update resources in MCP Fullstack — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Fullstack environment.

WHY IT NEEDS A POLICY

Why db.end_connection needs a policy

Ending a database connection is a reversible state change — it closes/tears down an active connection session. This is a Write-category action (modifying system state) rather than Destructive (no data is deleted) or Execute (no code/commands are run). Misuse could disrupt ongoing operations by terminating active DB sessions, hence medium severity.

From the tool's definition End a database connection

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

db.end_connection Rate-limited

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

FAQ

Questions about db.end_connection

What does the db.end_connection tool do? +

End a database connection. It is categorised as a Write tool in the MCP Fullstack MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

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

Register the MCP Fullstack MCP server in PolicyLayer and add a rule for db.end_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.end_connection? +

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

Can I rate-limit db.end_connection? +

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

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

db.end_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.