This record as markdown: /tools/ghl/update-social-post.md
What update_social_post does on Ghl
AI agents use update_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 | — | Updated tag IDs |
postId | string | Yes | Social media post ID |
status | string | — | Updated post status |
summary | string | — | Updated post content |
scheduleDate | string | — | Updated schedule date |
Parameters from the server's own tool schema.
Why update_social_post is rated Medium
This tool modifies existing social media content reversibly. It is a Write operation (not Read, as it changes data; not Destructive, as updates are reversible; not Execute/Financial/Other). Severity is medium because misuse could harm brand reputation or spread misinformation through modified posts, but the blast radius is limited to social media content for a single account.
From the tool's definition Tool name 'update_social_post' and description 'Update an existing social media post' indicate modification of existing data without deletion or financial impact.
Attacks that exploit this kind of access
The rule that runs update_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 update_social_post, this is the rule to start with:
update_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 update_social_post call is checked against it from then on.
Questions about update_social_post
Update an existing social media post. 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.
update_social_post accepts 5 parameters: tags, postId, status, summary, scheduleDate. 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 update_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.
update_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 update_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 update_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.
update_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