confirm_users_batch · MCP PostgreSQL Server MCP

WHAT IT DOES

What confirm_users_batch does on MCP PostgreSQL Server

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

WHY IT NEEDS A POLICY

Why confirm_users_batch needs a policy

Based on the tool name pattern 'confirm_users_batch' and its sibling 'confirm_user', this tool likely performs a batch confirmation/validation of multiple users, which could be a Write operation (modifying user state). The empty description significantly reduces confidence. Given the server context of user management with PostgreSQL, confirming users likely updates their status in the database.

From the tool's definition Tool name 'confirm_users_batch' and sibling tool 'confirm_user' suggest a batch confirmation operation; description is empty and uninformative.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

confirm_users_batch Rate-limited

confirm_users_batch 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": {
    "confirm_users_batch": {
      "limits": [
        {
          "counter": "confirm_users_batch_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 PostgreSQL Server, so you can run agents against it safely.

FAQ

Questions about confirm_users_batch

What does the confirm_users_batch tool do? +

confirm_users_batch. It is categorised as a Write tool in the MCP PostgreSQL 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 confirm_users_batch? +

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

What risk level is confirm_users_batch? +

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

Can I rate-limit confirm_users_batch? +

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

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

confirm_users_batch is provided by the MCP PostgreSQL Server MCP server (shubham-mishra-remotedesk/mcp-personal-efforti). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.