This record as markdown: /tools/ghl/start-social-oauth.md
What start_social_oauth does on Ghl
AI agents invoke start_social_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 context |
userId | string | Yes | User ID initiating OAuth |
platform | string | Yes | Social media platform |
reconnect | boolean | — | Whether this is a reconnection |
Parameters from the server's own tool schema.
Why start_social_oauth is rated High
OAuth initiation is an Execute action because it launches an external operation (authentication handshake with a third-party social platform) and modifies application state (tokens, permissions, connected accounts). While not immediately destructive, it grants access rights and enables downstream actions on social media accounts.
From the tool's definition Tool initiates OAuth authentication flow for social media platforms. The description states 'Start OAuth process for social media platform' — this triggers an external authentication operation whose effects depend on which platform is specified and user…
Attacks that exploit this kind of access
The rule that runs start_social_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 start_social_oauth, this is the rule to start with:
start_social_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 start_social_oauth call is checked against it from then on.
Questions about start_social_oauth
Start OAuth process for social media platform. 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.
start_social_oauth accepts 4 parameters: page, userId, platform, reconnect. Required: userId, platform. 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 start_social_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.
start_social_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 start_social_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 start_social_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.
start_social_oauth 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