social_media_posting_get_social_media_statistics
Get Social Media Statistics
This record as markdown: /tools/aiwerk-mcp-server-ghl/social-media-posting-get-social-media-statistics.md
What social_media_posting_get_social_media_statistics does on Ghl
AI agents call social_media_posting_get_social_media_statistics 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
platforms | array | — | Array of social media platforms to filter analytics by. If not provided, all platforms will be included. NOTE: Linkedin (PAGE only) and Tiktok (BUSINESS only) a |
locationId | string | — | Location ID Defaults to GHL_LOCATION_ID when omitted. |
profileIds | array | Yes | Array of connected social media account IDs to fetch analytics for. This can be found as 'profileId' in /accounts api. |
Parameters from the server's own tool schema.
Why social_media_posting_get_social_media_statistics is rated Low
Even though social_media_posting_get_social_media_statistics only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs social_media_posting_get_social_media_statistics 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_get_social_media_statistics, this is the rule to start with:
social_media_posting_get_social_media_statistics 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 social_media_posting_get_social_media_statistics call is checked against it from then on.
Questions about social_media_posting_get_social_media_statistics
Get Social Media Statistics. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.
social_media_posting_get_social_media_statistics accepts 3 parameters: platforms, locationId, profileIds. Required: profileIds. 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_get_social_media_statistics: 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_get_social_media_statistics 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 social_media_posting_get_social_media_statistics 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_get_social_media_statistics. 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_get_social_media_statistics 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