This record as markdown: /tools/aiwerk-mcp-server-ghl/social-media-posting-start-instagram-oauth.md
What social_media_posting_start_instagram_oauth does on Ghl
AI agents invoke social_media_posting_start_instagram_oauth to trigger actions in Ghl. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
page | string | — | Page |
userId | string | Yes | User Id |
reconnect | string | — | Reconnect |
locationId | string | — | Location Id Defaults to GHL_LOCATION_ID when omitted. |
Parameters from the server's own tool schema.
Why social_media_posting_start_instagram_oauth is rated High
social_media_posting_start_instagram_oauth triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Attacks that exploit this kind of access
The rule that runs social_media_posting_start_instagram_oauth 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_start_instagram_oauth, this is the rule to start with:
social_media_posting_start_instagram_oauth stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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 social_media_posting_start_instagram_oauth call is checked against it from then on.
Questions about social_media_posting_start_instagram_oauth
Starts OAuth For Instagram Account. It is categorised as a Execute tool in the Ghl MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
social_media_posting_start_instagram_oauth accepts 4 parameters: page, userId, reconnect, locationId. Required: userId. 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 social_media_posting_start_instagram_oauth: 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.
social_media_posting_start_instagram_oauth is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the social_media_posting_start_instagram_oauth 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 social_media_posting_start_instagram_oauth. 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.
social_media_posting_start_instagram_oauth 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.
More on Ghl, and thousands of servers like it.
This server
Across the catalogue