query_user_meetings
AI agents call query_user_meetings 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 appears to retrieve meeting information for a user based on its name and the pattern of sibling tools that perform calendar and meeting queries. The empty description prevents higher confidence. Querying meeting details is a read operation with potential moderate severity due to calendar data sensitivity (reveals scheduling, attendees, topics) but no data modification or irreversible action.
From the tool's definition Tool name 'query_user_meetings' and context from sibling tools 'get_meeting_details' and 'get_user_calendar_insights' indicate retrieval of calendar/meeting data. Description is empty, reducing confidence.
Attacks that exploit this kind of access
query_user_meetings. 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 query_user_meetings: 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.
query_user_meetings 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 query_user_meetings 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 query_user_meetings. 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.
query_user_meetings 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 →