Get a single meeting by UUID — meeting detail in the Activity/Showing Lifecycle.
AI agents call qobrix_get_meeting 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 a single meeting record by its UUID from the Qobrix CRM system. It is a standard read operation that queries existing data with no side effects, no data modification, and no destructive actions.
From the tool's definition Tool name 'qobrix_get_meeting' with description 'Get a single meeting by UUID' indicates a retrieval operation. The server is explicitly described as 'read-only MCP server' and the tool performs a query/fetch operation without modifying data.
Attacks that exploit this kind of access
Get a single meeting by UUID — meeting detail in the Activity/Showing Lifecycle. 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_get_meeting: 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_get_meeting 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_get_meeting 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_get_meeting. 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_get_meeting 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 →