List meetings — bridges the Activity Tracking and Showing Lifecycle workflows.
AI agents call qobrix_list_meetings to retrieve information from Qobrix CRM MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or lists meeting records from the Qobrix CRM without creating, modifying, deleting, or executing external operations. It is a straightforward read query against existing CRM data, consistent with the server's read-only design. Low severity because listing data has minimal blast radius if misused by an agent.
From the tool's definition Tool name 'qobrix_list_meetings' contains 'list' which is a read operation. Server description explicitly states it is 'read-only' and provides tools to 'query' CRM data. The tool bridges workflows but performs no modification.
Attacks that exploit this kind of access
List meetings — bridges the Activity Tracking and Showing Lifecycle workflows. It is categorised as a Read tool in the Qobrix CRM MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Qobrix CRM MCP Server MCP server in PolicyLayer and add a rule for qobrix_list_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 Qobrix CRM MCP Server. Nothing to install.
qobrix_list_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 qobrix_list_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 qobrix_list_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.
qobrix_list_meetings is provided by the Qobrix CRM MCP Server MCP server (sharpsir-group/qobrix-crm-mcp). 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 →