resolve_users_batch
AI agents call resolve_users_batch to retrieve information from MCP PostgreSQL Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name implies batch resolution of users, analogous to the sibling 'resolve_user' tool which is likely a read/lookup operation. The server is described as providing user name resolution. However, the empty description lowers confidence. Batch operations on user data could involve writes, but given the context of 'resolve' (lookup/matching), Read is the most likely category.
From the tool's definition Tool name 'resolve_users_batch' and sibling tool 'resolve_user' suggest user lookup/resolution operations. The server description mentions 'fuzzy user lookup, batch operations' as read-oriented features.
Attacks that exploit this kind of access
resolve_users_batch. It is categorised as a Read tool in the MCP PostgreSQL Server MCP Server, which means it retrieves data without modifying state.
Register the MCP PostgreSQL Server MCP server in PolicyLayer and add a rule for resolve_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.
resolve_users_batch is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the resolve_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.
Set action: deny in the PolicyLayer policy for resolve_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.
resolve_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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →