Connect an Outreach account via OAuth. Takes no parameters — call with {}. Initiates OAuth flow — in standalone mode, opens a browser URL for sign-in. In bridge mode, delegates to the host app. WHEN TO USE: - No Outreach account is connected - Authentication errors from other tools - User asks to...
AI agents invoke outreach_connect_account to trigger actions in Apple Shortcuts. 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.
This tool triggers an external operation (OAuth authentication flow) by opening a browser URL or delegating to a host app. It doesn't merely read or write data — it executes an external process/action. Misuse could result in unauthorized account linking or phishing-style redirects, warranting medium severity.
From the tool's definition Initiates OAuth flow — in standalone mode, opens a browser URL for sign-in. In bridge mode, delegates to the host app.
Documented attack patterns abuse exactly the kind of access outreach_connect_account gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Apple Shortcuts, and nothing reaches the server without passing your rules. This is the rule we recommend for outreach_connect_account:
{
"version": "1",
"default": "deny",
"tools": {
"outreach_connect_account": {
"limits": [
{
"counter": "outreach_connect_account_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}outreach_connect_account 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.
Free to start. No card required.
Connect an Outreach account via OAuth. Takes no parameters — call with {}. Initiates OAuth flow — in standalone mode, opens a browser URL for sign-in. In bridge mode, delegates to the host app. WHEN TO USE: - No Outreach account is connected - Authentication errors from other tools - User asks to connect Outreach After connecting, verify with outreach_list_connected_accounts. It is categorised as a Execute tool in the Apple Shortcuts MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Apple Shortcuts MCP server in PolicyLayer and add a rule for outreach_connect_account: 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 Apple Shortcuts. Nothing to install.
outreach_connect_account 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 outreach_connect_account 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 outreach_connect_account. 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.
outreach_connect_account is provided by the Apple Shortcuts MCP server (@mindstone/mcp-server-apple-shortcuts). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Apple Shortcuts, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
423 Apple Shortcuts tools catalogued and risk-classified — across an index of 43,000+ MCP servers.