social_media_posting_edit_post

Edit post

SERVERGhl SOURCE@aiwerk/mcp-server-ghl

Medium RISK CLASS

Category Write

Parameters 122 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/aiwerk-mcp-server-ghl/social-media-posting-edit-post.md

WHAT IT DOES

What social_media_posting_edit_post does on Ghl

AI agents use social_media_posting_edit_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
`id`	string	Yes	Post Id
`tags`	array	—	Array of Tag Value
`type`	object	Yes	Post Type must be one of the following values: - post, story, reel
`media`	array	—	Post Media Data The limitations of media as per the platforms is provided through the reference link in API description
`status`	object	—	Status must be one of the following values: in_progress, draft, failed, published, scheduled, in_review, notification_sent, deleted
`userId`	string	—	User ID
`summary`	string	—	Post Content The limitations of content as per the platforms is provided through the reference link in API description
`createdBy`	string	—	Created By
`accountIds`	array	—	Account Ids
`categoryId`	string	—	Category Id
`locationId`	string	—	Location Id Defaults to GHL_LOCATION_ID when omitted.
`scheduleDate`	string	—	Schedule Date

Parameters from the server's own tool schema.

RISK

Why social_media_posting_edit_post is rated Medium

An AI agent can call social_media_posting_edit_post faster than any human can review: one bad instruction and it creates or modifies resources in Ghl by the hundred, each call as confident as the last.

Risk signalsAccepts URL/endpoint input (gmbPostDetails.url) · High parameter count (41 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs social_media_posting_edit_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 social_media_posting_edit_post, this is the rule to start with:

social_media_posting_edit_post Rate-limited

social_media_posting_edit_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "social_media_posting_edit_post": {
      "limits": [
        {
          "counter": "social_media_posting_edit_post_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Ghl, apply this rule, and every social_media_posting_edit_post call is checked against it from then on.

FAQ

Questions about social_media_posting_edit_post

What does the social_media_posting_edit_post tool do? +

Edit 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.

What parameters does social_media_posting_edit_post accept? +

social_media_posting_edit_post accepts 12 parameters: id, tags, type, media, status, userId, summary, createdBy, accountIds, categoryId, locationId, scheduleDate. Required: id, type. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on social_media_posting_edit_post? +

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

What risk level is social_media_posting_edit_post? +

social_media_posting_edit_post is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit social_media_posting_edit_post? +

Yes. Add a rate_limit block to the social_media_posting_edit_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 social_media_posting_edit_post completely? +

Set action: deny in the PolicyLayer policy for social_media_posting_edit_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 social_media_posting_edit_post? +

social_media_posting_edit_post 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.

KEEP EXPLORING

More on Ghl, and thousands of servers like it.

This server

All 569 Ghl tools →

Across the catalogue

edit_screen on Stitch MCP Server →team_manager_post_blackboard on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →