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 Pulsemcp Cms Admin without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool purely retrieves and queries CMS data without modification, deletion, or execution capabilities. It returns read-only summaries and metadata with no side effects. The absence of body content and the explicit read-only nature of list views confirm this is a basic data retrieval operation with minimal blast radius if misused.
From the tool's definition Tool performs 'Retrieve a paginated list of newsletter posts' with 'list view [that] does NOT include post body content'. Returns formatted metadata only (title, slug, status, category, author, date, description).
Attacks that exploit this kind of access
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 Pulsemcp Cms Admin MCP Server, which means it retrieves data without modifying state.
Register the Pulsemcp Cms Admin 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 Pulsemcp Cms Admin. 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 Pulsemcp Cms Admin MCP server (pulsemcp-cms-admin-mcp-server). 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 →