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

get-post

A read tool on the GoHighLevel MCP server.

SERVERGoHighLevel MCP Server SOURCEdrausal/gohighlevel-mcp
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/drausal-gohighlevel-mcp/get-post.md

What get-post does on GoHighLevel MCP Server

AI agents call get-post to retrieve information from GoHighLevel MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get-post is rated Low

This tool retrieves post data from GoHighLevel's system. It performs a read-only operation with no side effects, no data modification, no code execution, and no destructive actions. The minimal blast radius from misuse is limited to accessing potentially sensitive post information, but the operation itself is non-invasive and reversible.

From the tool's definition Tool name 'get-post' with description 'Get post' indicates a retrieval operation. The verb 'get' is a standard read operation that queries or fetches data without modification.

Questions about get-post

What does the get-post tool do? +

get-post is a read tool on the GoHighLevel MCP Server MCP server. It is categorised as a Read tool in the GoHighLevel MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get-post? +

Register the GoHighLevel MCP Server MCP server in PolicyLayer and add a rule for get-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 GoHighLevel MCP Server. Nothing to install.

What risk level is get-post? +

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

Can I rate-limit get-post? +

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

How do I block get-post completely? +

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

What MCP server provides get-post? +

get-post is provided by the GoHighLevel MCP Server MCP server (drausal/gohighlevel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on GoHighLevel MCP Server, and thousands of servers like it.

// 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 GoHighLevel MCP Server'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.