Medium Risk

done

Complete the task with a success flag and optional text. Returns: dict: A dictionary indicating completion status.

How to control done ↓

AI agents use done to create or update resources in Mcp Browser Use — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Browser Use environment.

Medium Risk

An AI agent can call done faster than any human can review — one bad instruction and it creates or modifies resources in Mcp Browser Use by the hundred, each call as confident as the last.

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

PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Browser Use, and nothing reaches the server without passing your rules. This is the rule we recommend for done:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "done": {
      "limits": [
        {
          "counter": "done_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

done stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Mcp Browser Use — 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.
LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the done tool do? +

Complete the task with a success flag and optional text. Returns: dict: A dictionary indicating completion status. It is categorised as a Write tool in the Mcp Browser Use MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on done? +

Register the Mcp Browser Use MCP server in PolicyLayer and add a rule for done: 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 Mcp Browser Use. Nothing to install.

What risk level is done? +

done is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit done? +

Yes. Add a rate_limit block to the done 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 done completely? +

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

done is provided by the Mcp Browser Use MCP server (vinayak-mehta/mcp-browser-use). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Browser Use tool call.

Deterministic rules across all 19 Mcp Browser Use tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

19 Mcp Browser Use tools catalogued and risk-classified — across an index of 42,500+ 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.