search_research_posts
Search published research posts associated with one or more research entities. This tool requires research entity UUIDs. If only entity names are known, first call search_research_entities to obtain candidate research entities and their UUIDs. Use only entity_uuid values copied exactly from searc...
This record as markdown: /tools/com-globalsourcepartners-emerging-markets-research/search-research-posts.md
What search_research_posts does on GlobalSource Partners MCP Server
AI agents call search_research_posts to retrieve information from GlobalSource Partners MCP Server 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 |
|---|---|---|---|
limit | integer | — | Maximum number of posts to return. Minimum 1, maximum 50, default 25. |
order | string | — | Sort results by publication time. Use 'published_descending' for newest first or 'published_ascending' for oldest first. Default is published_descending. |
cursor | string | — | Pagination cursor returned by a previous response. Use this to retrieve the next page of results. |
published_after | string | — | Only return posts published after this date and time (ISO 8601 format). |
published_before | string | — | Only return posts published before this date and time (ISO 8601 format). |
count_total_results | boolean | — | Whether to include the total number of matching posts. Use false unless the total count is specifically needed. Calculating the total count may increase respons |
research_entity_uuids | array | Yes | One or more research entity UUIDs to search against. This field is required. At least one research entity UUID must be supplied. Do not pass entity names. I |
Parameters from the server's own tool schema.
Why search_research_posts is rated Low
This tool performs a search query across published research posts, returning matching results without any side effects. It retrieves data based on entity identifiers with no ability to create, modify, delete, or execute operations. This is a straightforward read operation with minimal risk.
From the tool's definition Tool description states 'Search published research posts' and 'requires research entity UUIDs' with no mention of modification, deletion, or execution capabilities. The tool retrieves/queries existing research data only.
Attacks that exploit this kind of access
The rule that runs search_research_posts safely
PolicyLayer is an MCP gateway: it sits between your AI agents and GlobalSource Partners MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search_research_posts, this is the rule to start with:
search_research_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 GlobalSource Partners MCP Server, apply this rule, and every search_research_posts call is checked against it from then on.
Questions about search_research_posts
Search published research posts associated with one or more research entities. This tool requires research entity UUIDs. If only entity names are known, first call search_research_entities to obtain candidate research entities and their UUIDs. Use only entity_uuid values copied exactly from search_research_entities results. Never infer, guess, construct, or transform UUIDs from entity names. Use this tool only after selecting the most appropriate research entity from the search_research_entities results. Examples: - To find research about "United States", first call search_research_entities with "United States", review the returned matches, select the most appropriate entity, and then call this tool with the selected entity_uuid. - To find recent research about multiple entities, pass all selected entity_uuid values in research_entity_uuids. - To retrieve the next page of results, pass the previous response's next_cursor as cursor. Results can be filtered by publication date and retrieved using cursor-based pagination. It is categorised as a Read tool in the GlobalSource Partners MCP Server MCP Server, which means it retrieves data without modifying state.
search_research_posts accepts 7 parameters: limit, order, cursor, published_after, published_before, count_total_results, research_entity_uuids. Required: research_entity_uuids. The full parameter table on this page comes from the server's own tool schema.
Register the GlobalSource Partners MCP Server MCP server in PolicyLayer and add a rule for search_research_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 GlobalSource Partners MCP Server. Nothing to install.
search_research_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_research_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_research_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_research_posts is provided by the GlobalSource Partners MCP Server MCP server (https://www.globalsourcepartners.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on GlobalSource Partners MCP Server, and thousands of servers like it.
This server
Across the catalogue