search_social_posts
Search and filter social media posts across all platforms
This record as markdown: /tools/ghl/search-social-posts.md
What search_social_posts does on Ghl
AI agents call search_social_posts 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 |
|---|---|---|---|
skip | number | — | Number of posts to skip |
type | string | — | Filter posts by status |
limit | number | — | Number of posts to return |
toDate | string | Yes | End date (ISO format) |
accounts | string | — | Comma-separated account IDs to filter by |
fromDate | string | Yes | Start date (ISO format) |
postType | string | — | Type of post to search for |
includeUsers | boolean | — | Include user data in response |
Parameters from the server's own tool schema.
Why search_social_posts is rated Low
The tool performs a search and filtering operation, which retrieves or queries data without side effects. No creation, modification, deletion, code execution, or financial transactions are involved. This is a straightforward read-only operation.
From the tool's definition Tool name 'search_social_posts' and description 'Search and filter social media posts across all platforms' indicate data retrieval operations with no modification or execution capabilities.
Attacks that exploit this kind of access
The rule that runs search_social_posts 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 search_social_posts, this is the rule to start with:
search_social_posts 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 search_social_posts call is checked against it from then on.
Questions about search_social_posts
Search and filter social media posts across all platforms. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.
search_social_posts accepts 8 parameters: skip, type, limit, toDate, accounts, fromDate, postType, includeUsers. Required: toDate, fromDate. 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 search_social_posts: 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.
search_social_posts 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 search_social_posts 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 search_social_posts. 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.
search_social_posts 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