AI agents call meetingDetails to retrieve information from MeetGeek MCP 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 details (metadata, transcripts, or summaries) without modifying or deleting data. This is a Read operation with low severity since it only accesses information already stored in MeetGeek. No financial, destructive, or code execution risk is evident from the available context.
From the tool's definition Tool name 'meetingDetails' and sibling tools 'meetings', 'transcript', 'highlights', 'summary' all suggest retrieval of meeting information. The server description states it 'access[es]' meetings and their metadata.
Documented attack patterns abuse exactly the kind of access meetingDetails gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MeetGeek MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for meetingDetails:
{
"version": "1",
"default": "deny",
"tools": {
"meetingDetails": {}
}
}meetingDetails is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
meetingDetails. It is categorised as a Read tool in the MeetGeek MCP Server MCP Server, which means it retrieves data without modifying state.
Register the MeetGeek MCP Server MCP server in PolicyLayer and add a rule for meetingDetails: 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 MeetGeek MCP Server. Nothing to install.
meetingDetails 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 meetingDetails 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 meetingDetails. 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.
meetingDetails is provided by the MeetGeek MCP Server MCP server (meetgeekai/meetgeek-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MeetGeek MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
6 MeetGeek MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.