High Risk →

browser_forward

Navigate forward in browser history.

How to control browser_forward ↓

What browser_forward does on Apple Shortcuts

AI agents invoke browser_forward 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.

High Risk

Why browser_forward needs a policy

This tool triggers a browser action (navigating forward in browser history), which is an external operation with side effects depending on the current browser state. It falls under Execute as it controls browser behavior rather than simply reading or writing data.

From the tool's definition Navigate forward in browser history

Documented attack patterns abuse exactly the kind of access browser_forward gives an agent:

How to control browser_forward

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_forward:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "browser_forward": {
      "limits": [
        {
          "counter": "browser_forward_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

browser_forward 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.

  1. Create a free account and register Apple Shortcuts — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about browser_forward

What does the browser_forward tool do? +

Navigate forward in browser history. 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.

How do I enforce a policy on browser_forward? +

Register the Apple Shortcuts MCP server in PolicyLayer and add a rule for browser_forward: 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.

What risk level is browser_forward? +

browser_forward is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit browser_forward? +

Yes. Add a rate_limit block to the browser_forward 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.

How do I block browser_forward completely? +

Set action: deny in the PolicyLayer policy for browser_forward. 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.

What MCP server provides browser_forward? +

browser_forward 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.

Enforce policy on every Apple Shortcuts tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.