get_free_busy
Check availability/free-busy status for users.
This record as markdown: /tools/freshdesk/get-free-busy.md
What get_free_busy does on Freshdesk
AI agents call get_free_busy 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 get_free_busy is rated Low
This tool retrieves and reads availability status information. There are no side effects, data modifications, deletions, code execution, or financial implications. It is a pure read operation that queries user availability, fitting squarely in the Read category with low severity due to minimal potential for misuse.
From the tool's definition Tool name 'get_free_busy' and description 'Check availability/free-busy status for users' indicate a query operation that retrieves calendar availability data without modifying or deleting anything.
Attacks that exploit this kind of access
The rule that runs get_free_busy 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 get_free_busy, this is the rule to start with:
get_free_busy 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 get_free_busy call is checked against it from then on.
Questions about get_free_busy
Check availability/free-busy status for users. 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 get_free_busy: 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.
get_free_busy 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 get_free_busy 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 get_free_busy. 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.
get_free_busy 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