Retrieve complete details for a specific newsletter post by its unique slug identifier. Returns formatted markdown with all post metadata and content. The response is formatted as markdown with sections for: - Post title and basic metadata (slug, status, category, author(s), dates) - Summary/shor...
AI agents call get_newsletter_post 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 a straightforward query operation to fetch and return existing newsletter post data. There is no creation, modification, deletion, or execution of code/commands. The only argument is a slug identifier used to specify which post to retrieve.
From the tool's definition Tool description states it 'Retrieve[s] complete details for a specific newsletter post' and 'Returns formatted markdown with all post metadata and content.' The verb 'retrieve' and the read-only nature of querying existing newsletter posts by slug identifier…
Documented attack patterns abuse exactly the kind of access get_newsletter_post 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_newsletter_post:
{
"version": "1",
"default": "deny",
"tools": {
"get_newsletter_post": {}
}
}get_newsletter_post 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 complete details for a specific newsletter post by its unique slug identifier. Returns formatted markdown with all post metadata and content. The response is formatted as markdown with sections for: - Post title and basic metadata (slug, status, category, author(s), dates) - Summary/short description - Full HTML content (body field) as raw HTML - Complete metadata including all URLs, SEO tags, and featured items - Table of contents (if available) as raw HTML All available fields from the post are included: - title, slug, status, category - authors (ordered list; the primary author is listed first) - created_at, updated_at, last_updated - short_title, short_description - body (raw HTML content) - table_of_contents (raw HTML) - image_url, preview_image_url, share_image - title_tag, description_tag - featured_mcp_server_ids, featured_mcp_client_ids Status meanings: - draft: Unpublished posts that are being written or edited - live: Published posts visible on the website Use cases: - View the complete content of a specific newsletter post - Check the current status and metadata of a post before editing - Retrieve SEO fields for optimization or analysis - Get the full HTML content for preview or export - Review featured MCP servers and clients associated with a post - Verify author information and timestamps. 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_newsletter_post: 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_newsletter_post 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_newsletter_post 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_newsletter_post. 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_newsletter_post 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.