Close an existing Twist thread with an optional closing message. This tool marks a thread as closed, preventing further replies while keeping the thread accessible for reference. A closing message is automatically added to indicate the thread has been closed. Example response: Successfully closed...
AI agents use close_thread to create or update resources in Playwright Stealth — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Playwright Stealth environment.
The tool modifies the state of an existing thread by closing it, which is a write operation. It is not destructive since the thread remains accessible and the action could be undone by reopening it. The severity is medium because closing a thread prevents collaboration but doesn't delete data or trigger external actions; however, it could disrupt communication if misused on important discussions.
From the tool's definition Tool description states it "marks a thread as closed" and "prevents further replies". This is a reversible modification of thread state/metadata (closing), not a deletion. The closing message is also added/modified.
Documented attack patterns abuse exactly the kind of access close_thread gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Playwright Stealth, and nothing reaches the server without passing your rules. This is the rule we recommend for close_thread:
{
"version": "1",
"default": "deny",
"tools": {
"close_thread": {
"limits": [
{
"counter": "close_thread_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}close_thread 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.
Free to start. No card required.
Close an existing Twist thread with an optional closing message. This tool marks a thread as closed, preventing further replies while keeping the thread accessible for reference. A closing message is automatically added to indicate the thread has been closed. Example response: Successfully closed thread: - Thread ID: 789012 - Closing message:. It is categorised as a Write tool in the Playwright Stealth MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Playwright Stealth MCP server in PolicyLayer and add a rule for close_thread: 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 Stealth. Nothing to install.
close_thread is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the close_thread 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 close_thread. 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.
close_thread is provided by the Playwright Stealth MCP server (pulsemcp/mcp-servers). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Playwright Stealth, 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.
68 Playwright Stealth tools catalogued and risk-classified — across an index of 43,000+ MCP servers.