Check Slack connection status. Call FIRST before any Slack operation. Returns: - connected: true/false - workspaces: array of connected workspaces with team names - tokenHealth: bot/user token status (valid|missing|refreshable|expired) CRITICAL: If response shows connected=false, call authenticat...
AI agents call list_slack_workspaces to retrieve information from Apple Shortcuts without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only operation that queries and returns the status of Slack workspace connections and token health. It has no ability to modify, execute, delete, or commit financial actions. The mention of OAuth flow in error cases is informational guidance only; the tool itself does not perform authentication. Severity is low because even if misused, an agent can only observe connection metadata without causing harm.
From the tool's definition Tool name 'list_slack_workspaces' and description states it 'Check[s] Slack connection status' and 'Returns' connection status and workspace information. The operation is a query/check with no side effects—it retrieves state information only.
Documented attack patterns abuse exactly the kind of access list_slack_workspaces 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 list_slack_workspaces:
{
"version": "1",
"default": "deny",
"tools": {
"list_slack_workspaces": {}
}
}list_slack_workspaces is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Check Slack connection status. Call FIRST before any Slack operation. Returns: - connected: true/false - workspaces: array of connected workspaces with team names - tokenHealth: bot/user token status (valid|missing|refreshable|expired) CRITICAL: If response shows connected=false, call authenticate_slack_workspace to start the connection flow. The host will guide the user through OAuth. It is categorised as a Read tool in the Apple Shortcuts MCP Server, which means it retrieves data without modifying state.
Register the Apple Shortcuts MCP server in PolicyLayer and add a rule for list_slack_workspaces: 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.
list_slack_workspaces 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_slack_workspaces 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_slack_workspaces. 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_slack_workspaces 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.