get_meeting_details
AI agents call get_meeting_details 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.
Based on naming convention and context from sibling tools on a PostgreSQL user/team management server, this tool retrieves meeting details without modifying, executing, or deleting data. The empty description lowers confidence slightly, but the semantic pattern is clear: 'get_X' functions are typically read operations. No side effects, destructive actions, code execution, or financial operations are implied.
From the tool's definition Tool name 'get_meeting_details' indicates retrieval of meeting information. Description is empty, limiting direct evidence.
Attacks that exploit this kind of access
get_meeting_details. 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 get_meeting_details: 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.
get_meeting_details 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 get_meeting_details 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 get_meeting_details. 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.
get_meeting_details 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 →