Disconnect a connected social account from posterly. DESTRUCTIVE and IRREVERSIBLE: removes the account connection, emits account.disconnected webhooks, and may transfer Instagram scheduled posts to a replacement account.\n\n
AI agents call disconnect_account to permanently remove resources in Posterly — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Disconnecting a social account is an irreversible action that removes access to account integrations and modifies the state of scheduled content. While not deleting data outright, it permanently severs a critical connection. This fits the Destructive category as the action cannot be undone without manual reconnection and potential loss of context.
From the tool's definition The description explicitly states 'DESTRUCTIVE and IRREVERSIBLE: removes the account connection' and notes it may transfer scheduled posts. The tool severs an integration that cannot be easily undone without re-authentication.
Attacks that exploit this kind of access
Disconnect a connected social account from posterly. DESTRUCTIVE and IRREVERSIBLE: removes the account connection, emits account.disconnected webhooks, and may transfer Instagram scheduled posts to a replacement account.\n\n. It is categorised as a Destructive tool in the Posterly MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Posterly MCP server in PolicyLayer and add a rule for disconnect_account: 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 Posterly. Nothing to install.
disconnect_account 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 disconnect_account 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 disconnect_account. 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.
disconnect_account is provided by the Posterly MCP server (posterly-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →