Close the browser session. Sessions are saved automatically.
AI agents invoke browser_close 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.
Closing a browser session is an external operation that terminates an active session. While sessions are saved automatically (reducing destructive risk), this action triggers an external side effect (ending the browser session) that cannot be trivially undone mid-task. It fits Execute as it triggers an external operation.
From the tool's definition Close the browser session. Sessions are saved automatically.
Documented attack patterns abuse exactly the kind of access browser_close 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 browser_close:
{
"version": "1",
"default": "deny",
"tools": {
"browser_close": {
"limits": [
{
"counter": "browser_close_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} browser_close 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.
Close the browser session. Sessions are saved automatically. 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 browser_close: 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.
browser_close 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 browser_close 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 browser_close. 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.
browser_close 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.