Retrieve a complete thread conversation including all messages. This tool fetches the full context of a discussion, showing the thread metadata and every message posted in chronological order. Essential for understanding the complete conversation history. Example response: Thread:
AI agents call get_thread to retrieve information from Playwright Stealth without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs data retrieval only. It accesses and returns thread metadata and messages in chronological order without modifying, deleting, or executing any actions. The example response shows output-only behavior. This is a straightforward Read category operation with minimal risk if misused by an AI agent, as it cannot cause side effects beyond unauthorized information access.
From the tool's definition Tool description states 'Retrieve a complete thread conversation' and 'fetches the full context of a discussion, showing the thread metadata and every message posted' — core read operations with no modification, deletion, or execution.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access get_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 get_thread:
{
"version": "1",
"default": "deny",
"tools": {
"get_thread": {}
}
}get_thread is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Retrieve a complete thread conversation including all messages. This tool fetches the full context of a discussion, showing the thread metadata and every message posted in chronological order. Essential for understanding the complete conversation history. Example response: Thread:. It is categorised as a Read tool in the Playwright Stealth MCP Server, which means it retrieves data without modifying state.
Register the Playwright Stealth MCP server in PolicyLayer and add a rule for get_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.
get_thread is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_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 get_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.
get_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.