get_blog_posts
Get blog posts from a specific blog site. Use this to list and search existing blog posts.
This record as markdown: /tools/ghl/get-blog-posts.md
What get_blog_posts does on Ghl
AI agents call get_blog_posts to retrieve information from Ghl without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | number | — | Number of posts to retrieve (default: 10, max recommended: 50) |
blogId | string | Yes | Blog site ID to get posts from (use get_blog_sites to find available blogs) |
offset | number | — | Number of posts to skip for pagination (default: 0) |
status | string | — | Optional filter by publication status |
searchTerm | string | — | Optional search term to filter posts by title or content |
Parameters from the server's own tool schema.
Why get_blog_posts is rated Low
This tool retrieves blog post data without creating, modifying, or deleting anything. The verbs 'Get', 'list', and 'search' are hallmarks of Read operations. Even though the server includes destructive tools like 'bulk_delete_social_posts', this specific tool is purely a retrieval operation with minimal blast radius if misused.
From the tool's definition Tool description explicitly states 'Get blog posts' and 'list and search existing blog posts' — retrieval operations with no side effects.
Attacks that exploit this kind of access
The rule that runs get_blog_posts safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ghl, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_blog_posts, this is the rule to start with:
get_blog_posts is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Ghl, apply this rule, and every get_blog_posts call is checked against it from then on.
Questions about get_blog_posts
Get blog posts from a specific blog site. Use this to list and search existing blog posts. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.
get_blog_posts accepts 5 parameters: limit, blogId, offset, status, searchTerm. Required: blogId. The full parameter table on this page comes from the server's own tool schema.
Register the Ghl MCP server in PolicyLayer and add a rule for get_blog_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 Ghl. Nothing to install.
get_blog_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_blog_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_blog_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_blog_posts is provided by the Ghl MCP server (ghl-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ghl, and thousands of servers like it.
This server
Across the catalogue