list_events
List calendar events within a date range. Returns JSON by default (with timezoneInfo showing calendar, device, and resolved timezone). Set returnText=true for a human-readable agenda format. Pass deviceTimezone from the system prompt for fallback if calendar settings are unavailable.
This record as markdown: /tools/freshdesk/list-events.md
What list_events does on Freshdesk
AI agents call list_events to retrieve information from Freshdesk without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_events is rated Low
This tool purely queries and retrieves calendar event data within a specified date range. It has no parameters that would cause data modification, deletion, or execution of external operations. The return of timezone information and formatting options (JSON vs. text) are presentation choices, not functional changes.
From the tool's definition Tool description states 'List calendar events' which is a retrieval operation. Returns data in JSON or human-readable format with no modification, creation, deletion, or side effects mentioned.
Attacks that exploit this kind of access
The rule that runs list_events safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Freshdesk, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_events, this is the rule to start with:
list_events is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Freshdesk, apply this rule, and every list_events call is checked against it from then on.
Questions about list_events
List calendar events within a date range. Returns JSON by default (with timezoneInfo showing calendar, device, and resolved timezone). Set returnText=true for a human-readable agenda format. Pass deviceTimezone from the system prompt for fallback if calendar settings are unavailable. It is categorised as a Read tool in the Freshdesk MCP Server, which means it retrieves data without modifying state.
Register the Freshdesk MCP server in PolicyLayer and add a rule for list_events: 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 Freshdesk. Nothing to install.
list_events 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_events 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_events. 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_events is provided by the Freshdesk MCP server (@mindstone-engineering/mcp-server-freshdesk). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Freshdesk, and thousands of servers like it.
This server
Across the catalogue