This record as markdown: /tools/ghl/delete-social-post.md
What delete_social_post does on Ghl
AI agents call delete_social_post to permanently remove resources in Ghl, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
postId | string | Yes | Social media post ID to delete |
Parameters from the server's own tool schema.
Why delete_social_post is rated Critical
This tool irreversibly removes social media content. Once deleted, the post cannot be recovered through normal means. This is a destructive action with no undo capability. While the blast radius is limited to a single post (not organizational-level data), the permanent nature of deletion and potential reputational/compliance impact justifies 'high' severity.
From the tool's definition Tool name is 'delete_social_post' and description states 'Delete a social media post' — uses the verb 'delete' which indicates irreversible removal of data.
Attacks that exploit this kind of access
The rule that runs delete_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 delete_social_post, this is the rule to start with:
delete_social_post is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Ghl, apply this rule, and every delete_social_post call is checked against it from then on.
Questions about delete_social_post
Delete a social media post. It is categorised as a Destructive tool in the Ghl MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete_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 delete_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.
delete_social_post is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_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 delete_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.
delete_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.
Across the catalogue