Retrieve a paginated list of newsletter posts from the PulseMCP CMS. Returns formatted markdown with post summaries and metadata. The response is formatted as markdown with: - Total count and pagination info - Numbered list of posts, each showing: - Title and slug - Status and category - Author n...
AI agents call get_newsletter_posts 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 is a straightforward data retrieval operation with no side effects. It queries an existing CMS system to fetch and display post information in a read-only manner. The tool has minimal blast radius—even if an AI agent misuses it, the worst outcome is retrieving posts it shouldn't have access to, which would be a data confidentiality issue but not destructive or operationally damaging.
From the tool's definition Tool retrieves a paginated list of newsletter posts with metadata (title, slug, status, category, author, date, description) but explicitly does NOT include post body content. Returns formatted markdown summaries only.
Documented attack patterns abuse exactly the kind of access get_newsletter_posts 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_posts:
{
"version": "1",
"default": "deny",
"tools": {
"get_newsletter_posts": {}
}
}get_newsletter_posts 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 paginated list of newsletter posts from the PulseMCP CMS. Returns formatted markdown with post summaries and metadata. The response is formatted as markdown with: - Total count and pagination info - Numbered list of posts, each showing: - Title and slug - Status and category - Author name (if available) - Created date - Short description (if available) Note: The list view does NOT include post body content. Use get_newsletter_post to retrieve full post details. Status meanings: - draft: Unpublished posts that are being written or edited - live: Published posts visible on the website Use cases: - Browse all newsletter posts before creating new content to avoid duplicates - Search for posts on specific topics or by specific authors - Find draft posts that need to be completed or published - Review recent posts to maintain consistency in style and topics - Check the status of posts created by team members - Export post metadata for reporting or analytics. 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_posts: 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_posts 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_posts 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_posts. 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_posts 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.