# 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.

Agent View of the PolicyLayer registry record for `search_research_posts`. HTML page: https://policylayer.com/tools/com-globalsourcepartners-emerging-markets-research/search-research-posts

## Facts

- Tool: `search_research_posts`
- Server: GlobalSource Partners MCP Server (`https://www.globalsourcepartners.com/mcp`) — https://policylayer.com/tools/com-globalsourcepartners-emerging-markets-research.md
- Homepage: https://github.com/https://www.globalsourcepartners.com/mcp
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 7 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `limit` | integer | no | Maximum number of posts to return. Minimum 1, maximum 50, default 25. |
| `order` | string | no | Sort results by publication time. Use 'published_descending' for newest first or 'published_ascending' for oldest first. Default is published_descending. |
| `cursor` | string | no | Pagination cursor returned by a previous response. Use this to retrieve the next page of results. |
| `published_after` | string | no | Only return posts published after this date and time (ISO 8601 format). |
| `published_before` | string | no | Only return posts published before this date and time (ISO 8601 format). |
| `count_total_results` | boolean | no | 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.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "search_research_posts",
    "arguments": {
      "research_entity_uuids": []
    }
  }
}
```

## 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 own 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."

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches GlobalSource Partners MCP Server:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "search_research_posts": {}
  }
}
```

## Other tools on GlobalSource Partners MCP Server (3)

- `read_research_author` — Read — https://policylayer.com/tools/com-globalsourcepartners-emerging-markets-research/read-research-author.md
- `read_research_post` — Read — https://policylayer.com/tools/com-globalsourcepartners-emerging-markets-research/read-research-post.md
- `search_research_entities` — Read — https://policylayer.com/tools/com-globalsourcepartners-emerging-markets-research/search-research-entities.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=com-globalsourcepartners-emerging-markets-research · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-globalsourcepartners-emerging-markets-research