Lists all calendars available to the authenticated user.
AI agents call list_calendars 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 performs a simple query/list operation to retrieve calendar information for the authenticated user. It does not modify, delete, execute, or create any data. The operation is read-only and returns existing calendar metadata. The severity is low as exposure would only leak calendar list information, not sensitive event details or enable harmful actions.
From the tool's definition Tool name 'list_calendars' and description 'Lists all calendars available to the authenticated user' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
Lists all calendars available to the authenticated user. 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 list_calendars: 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.
list_calendars 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 list_calendars 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 list_calendars. 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.
list_calendars 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 →