create_social_post
Create a new social media post for multiple platforms
This record as markdown: /tools/ghl/create-social-post.md
What create_social_post does on Ghl
AI agents use create_social_post to create or update resources in Ghl, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ghl environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
tags | array | — | Tag IDs to associate with post |
type | string | Yes | Type of post |
media | array | — | Media attachments |
status | string | — | Post status |
userId | string | — | User ID creating the post |
summary | string | Yes | Post content/text |
accountIds | array | Yes | Array of social media account IDs to post to |
categoryId | string | — | Category ID |
scheduleDate | string | — | Schedule date for post (ISO format) |
followUpComment | string | — | Follow-up comment |
Parameters from the server's own tool schema.
Why create_social_post is rated Medium
This tool creates new social media posts, which is a write operation that modifies data (adds posts to social media accounts). It is reversible since posts can be edited or deleted later, distinguishing it from destructive operations.
From the tool's definition Tool name 'create_social_post' and description 'Create a new social media post for multiple platforms' indicate creation of new content that is reversible (posts can be edited or deleted).
Risk signalsAccepts URL/endpoint input (media[].url) · High parameter count (13 properties)
Attacks that exploit this kind of access
The rule that runs create_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 create_social_post, this is the rule to start with:
create_social_post stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 create_social_post call is checked against it from then on.
Questions about create_social_post
Create a new social media post for multiple platforms. It is categorised as a Write tool in the Ghl MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_social_post accepts 10 parameters: tags, type, media, status, userId, summary, accountIds, categoryId, scheduleDate, followUpComment. Required: type, summary, accountIds. 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 create_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.
create_social_post is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_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 create_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.
create_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