Query calendar items for a lead (v2 API). Requires leadId.
AI agents call queryCalendars to retrieve information from Lofty MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries/retrieves calendar data for a specific lead identified by leadId. The verb 'query' and the absence of any language indicating creation, modification, deletion, or execution of external operations classifies this as a Read operation. The severity is low because retrieving calendar metadata poses minimal risk—it does not alter data, execute code, or trigger financial transactions.
From the tool's definition Tool name 'queryCalendars' and description 'Query calendar items for a lead' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Query calendar items for a lead (v2 API). Requires leadId. It is categorised as a Read tool in the Lofty MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Lofty MCP Server MCP server in PolicyLayer and add a rule for queryCalendars: 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 Lofty MCP Server. Nothing to install.
queryCalendars 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 queryCalendars 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 queryCalendars. 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.
queryCalendars is provided by the Lofty MCP Server MCP server (nerdsnipe-inc/lofty-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 →