stop_call
Stop an ongoing call immediately. WHEN TO USE: - User wants to end a call in progress - Call is stuck or behaving unexpectedly - Emergency stop COMMON MISTAKES: - Calling this on an already ended call; use get_call first if unsure ERROR RECOVERY: - 401: API key is missing or invalid → configure_r...
This record as markdown: /tools/freshdesk/stop-call.md
What stop_call does on Freshdesk
AI agents invoke stop_call to trigger actions in Freshdesk. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why stop_call is rated High
This tool triggers an external operation (terminating a VoIP or communication call) whose effects are immediate and depend on the call_id argument. While not destructive (the call state can theoretically be restarted), it executes a command that affects live infrastructure and user experience. It fits Execute rather than Write because it's an imperative action on external state rather than data creation/modification.
From the tool's definition Tool description states 'Stop an ongoing call immediately' and explicitly lists 'Emergency stop' as a use case. This performs a real-time action with external effects on an active communication channel.
Attacks that exploit this kind of access
The rule that runs stop_call 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 stop_call, this is the rule to start with:
stop_call stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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 stop_call call is checked against it from then on.
Questions about stop_call
Stop an ongoing call immediately. WHEN TO USE: - User wants to end a call in progress - Call is stuck or behaving unexpectedly - Emergency stop COMMON MISTAKES: - Calling this on an already ended call; use get_call first if unsure ERROR RECOVERY: - 401: API key is missing or invalid → configure_retell_api_key - 404: call_id not found or no longer active → verify with list_calls/get_call RELATED TOOLS: - get_call: Check whether status is. It is categorised as a Execute tool in the Freshdesk MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Freshdesk MCP server in PolicyLayer and add a rule for stop_call: 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.
stop_call is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the stop_call 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 stop_call. 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.
stop_call 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.
Across the catalogue