apple_shortcuts_run
Run a named Apple Shortcut, optionally with text input. Use this tool to execute any shortcut the user has in their Shortcuts library. Args: - name (string): The exact name or identifier of the shortcut to run. - input (string, optional): Text content to pass to the shortcut. Pass the literal tex...
This record as markdown: /tools/freshdesk/apple-shortcuts-run.md
What apple_shortcuts_run does on Freshdesk
AI agents invoke apple_shortcuts_run 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 apple_shortcuts_run is rated High
This tool executes external operations (Apple Shortcuts) whose effects depend entirely on what shortcuts are defined in the user's library. A shortcut could perform any action the user has configured—file operations, network calls, system commands, or integrations with other applications.
From the tool's definition Tool description states 'Run a named Apple Shortcut' and 'execute any shortcut the user has in their Shortcuts library.' The tool invokes arbitrary user-defined automation workflows on macOS.
Attacks that exploit this kind of access
The rule that runs apple_shortcuts_run 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 apple_shortcuts_run, this is the rule to start with:
apple_shortcuts_run 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 apple_shortcuts_run call is checked against it from then on.
Questions about apple_shortcuts_run
Run a named Apple Shortcut, optionally with text input. Use this tool to execute any shortcut the user has in their Shortcuts library. Args: - name (string): The exact name or identifier of the shortcut to run. - input (string, optional): Text content to pass to the shortcut. Pass the literal text — the connector writes it to a private temporary file and hands that path to the macOS \. 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 apple_shortcuts_run: 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.
apple_shortcuts_run 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 apple_shortcuts_run 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 apple_shortcuts_run. 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.
apple_shortcuts_run 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