New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

blogs_get_all_blog_authors_by_location

Get all authors

SERVERGhl SOURCE@aiwerk/mcp-server-ghl
Low RISK CLASS
Category Read
Parameters 32 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/aiwerk-mcp-server-ghl/blogs-get-all-blog-authors-by-location.md

What blogs_get_all_blog_authors_by_location does on Ghl

AI agents call blogs_get_all_blog_authors_by_location 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.

ParameterTypeRequiredDescription
limit number Yes Number of authors to show in the listing
offset number Yes Number of authors to skip in listing
locationId string Location Id Defaults to GHL_LOCATION_ID when omitted.

Parameters from the server's own tool schema.

Why blogs_get_all_blog_authors_by_location is rated Low

Even though blogs_get_all_blog_authors_by_location 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.

Questions about blogs_get_all_blog_authors_by_location

What does the blogs_get_all_blog_authors_by_location tool do? +

Get all authors. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.

What parameters does blogs_get_all_blog_authors_by_location accept? +

blogs_get_all_blog_authors_by_location accepts 3 parameters: limit, offset, locationId. Required: limit, offset. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on blogs_get_all_blog_authors_by_location? +

Register the Ghl MCP server in PolicyLayer and add a rule for blogs_get_all_blog_authors_by_location: 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.

What risk level is blogs_get_all_blog_authors_by_location? +

blogs_get_all_blog_authors_by_location is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit blogs_get_all_blog_authors_by_location? +

Yes. Add a rate_limit block to the blogs_get_all_blog_authors_by_location 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.

How do I block blogs_get_all_blog_authors_by_location completely? +

Set action: deny in the PolicyLayer policy for blogs_get_all_blog_authors_by_location. 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.

What MCP server provides blogs_get_all_blog_authors_by_location? +

blogs_get_all_blog_authors_by_location 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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Ghl's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.