close_database · Re MCP: Risk & Policy

WHAT IT DOES

What close_database does on Re

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

WHY IT NEEDS A POLICY

Why close_database needs a policy

Despite the empty description, the semantics of 'close_database' indicate a Write-category operation: it modifies the state of an open resource connection reversibly. It does not retrieve data (Read), delete data (Destructive), move money (Financial), or execute arbitrary code (Execute).

From the tool's definition Tool name 'close_database' suggests closing/releasing a database connection or resource. While the description is empty, the action of closing a database is a reversible state change (the database remains intact; only the connection is terminated).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

close_database Rate-limited

close_database 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": {
    "close_database": {
      "limits": [
        {
          "counter": "close_database_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 Re, so you can run agents against it safely.

FAQ

Questions about close_database

What does the close_database tool do? +

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

How do I enforce a policy on close_database? +

Register the Re MCP server in PolicyLayer and add a rule for close_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 Re. Nothing to install.

What risk level is close_database? +

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

Can I rate-limit close_database? +

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

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

close_database is provided by the Re MCP server (jtsylve/re-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.