This record as markdown: /tools/aiwerk-mcp-server-ghl/blogs-get-blog-post.md
What blogs_get_blog_post does on Ghl
AI agents call blogs_get_blog_post 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 | Yes | |
blogId | string | Yes | |
offset | number | Yes | |
status | string | — | |
locationId | string | — | Defaults to GHL_LOCATION_ID when omitted. |
searchTerm | string | — | search for any post by name |
Parameters from the server's own tool schema.
Why blogs_get_blog_post is rated Low
Even though blogs_get_blog_post only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs blogs_get_blog_post 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 blogs_get_blog_post, this is the rule to start with:
blogs_get_blog_post 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 blogs_get_blog_post call is checked against it from then on.
Questions about blogs_get_blog_post
Get Blog posts by Blog ID. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.
blogs_get_blog_post accepts 6 parameters: limit, blogId, offset, status, locationId, searchTerm. Required: limit, blogId, offset. 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 blogs_get_blog_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 Ghl. Nothing to install.
blogs_get_blog_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 blogs_get_blog_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 blogs_get_blog_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.
blogs_get_blog_post is provided by the Ghl MCP server (@aiwerk/mcp-server-ghl). 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