get_blog_authors
Get all available blog authors for the current location. Use this to find author IDs for creating blog posts.
This record as markdown: /tools/ghl/get-blog-authors.md
What get_blog_authors does on Ghl
AI agents call get_blog_authors 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 authors to retrieve (default: 10) |
offset | number | — | Number of authors to skip for pagination (default: 0) |
Parameters from the server's own tool schema.
Why get_blog_authors is rated Low
This tool queries and returns existing blog author data without creating, modifying, deleting, or executing any action. It is a pure read operation with minimal risk even if misused by an agent.
From the tool's definition Tool description states 'Get all available blog authors' — a retrieval operation with no side effects. The purpose is informational lookup ('find author IDs') to support subsequent operations.
Attacks that exploit this kind of access
The rule that runs get_blog_authors 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_authors, this is the rule to start with:
get_blog_authors 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_authors call is checked against it from then on.
Questions about get_blog_authors
Get all available blog authors for the current location. Use this to find author IDs for creating blog posts. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.
get_blog_authors accepts 2 parameters: limit, 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 get_blog_authors: 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_authors 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_authors 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_authors. 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_authors 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