Call this tool when the task is complete.
AI agents call done as a supporting operation in Playwright MCP workflows.
This tool appears to be a control-flow or signaling tool that indicates task completion. It does not read, write, execute, delete, or move money. It is a terminal/sentinel action with no described data manipulation or external operation.
From the tool's definition 'Call this tool when the task is complete' — signals task completion with no described side effects
Attacks that exploit this kind of access
Call this tool when the task is complete. It is categorised as a Other tool in the Playwright MCP MCP Server, which means it performs auxiliary operations.
Register the Playwright 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 Playwright MCP. Nothing to install.
done is a Other tool with low risk. Read-only tools are generally safe to allow by default.
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.
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.
done is provided by the Playwright MCP server (nzjami/mcpplaywright). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →