Queries free/busy information for one or more calendars within a specified time range.
AI agents call query_calendar_freebusy to retrieve information from Langfuse Observability without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves calendar availability data (free/busy status) without creating, modifying, deleting, or executing actions. It is a pure read operation on calendar state within a specified time range. Even if misused by an AI agent, it only leaks scheduling information with minimal security impact.
From the tool's definition Tool name includes 'query' and description states it 'Queries free/busy information' — a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Queries free/busy information for one or more calendars within a specified time range. It is categorised as a Read tool in the Langfuse Observability MCP Server, which means it retrieves data without modifying state.
Register the Langfuse Observability MCP server in PolicyLayer and add a rule for query_calendar_freebusy: 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 Langfuse Observability. Nothing to install.
query_calendar_freebusy 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 query_calendar_freebusy 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 query_calendar_freebusy. 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.
query_calendar_freebusy is provided by the Langfuse Observability MCP server (langfuse-observability-mcp-server). 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 →