get_social_accounts
Get all connected social media accounts and groups
This record as markdown: /tools/ghl/get-social-accounts.md
What get_social_accounts does on Ghl
AI agents call get_social_accounts to retrieve information from Ghl without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_social_accounts is rated Low
This tool queries and retrieves existing data about connected social media accounts without any side effects. It performs a read-only operation similar to a list or fetch action, making it a Read category tool. The severity is low because retrieving account metadata poses minimal risk even if misused by an agent.
From the tool's definition Tool name is 'get_social_accounts' and description states 'Get all connected social media accounts and groups' — explicit retrieval with no modification or deletion.
Attacks that exploit this kind of access
The rule that runs get_social_accounts 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 get_social_accounts, this is the rule to start with:
get_social_accounts is read-only, so it stays allowed. 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 get_social_accounts call is checked against it from then on.
Questions about get_social_accounts
Get all connected social media accounts and groups. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.
Register the Ghl MCP server in PolicyLayer and add a rule for get_social_accounts: 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.
get_social_accounts is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_social_accounts 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 get_social_accounts. 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.
get_social_accounts 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