This record as markdown: /tools/ghl/get-social-post.md
What get_social_post does on Ghl
AI agents call get_social_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 |
|---|---|---|---|
postId | string | Yes | Social media post ID |
Parameters from the server's own tool schema.
Why get_social_post is rated Low
This tool retrieves information about a social media post without creating, modifying, or deleting any data. It is a straightforward read operation with minimal risk if misused by an AI agent—at worst, it could retrieve posts the agent shouldn't have access to, but no data is altered or destroyed.
From the tool's definition Tool name 'get_social_post' and description 'Get details of a specific social media post' indicate retrieval of existing data with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs get_social_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 get_social_post, this is the rule to start with:
get_social_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 get_social_post call is checked against it from then on.
Questions about get_social_post
Get details of a specific social media post. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.
get_social_post accepts 1 parameter: postId. Required: postId. 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_social_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.
get_social_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 get_social_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 get_social_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.
get_social_post 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