# read_research_author

Read a single research author by author UUID. Use this tool when a user wants profile details for a specific research author returned by another research tool. The response includes author metadata, biography fields, profile URL, and visible sectors associated with the author. Missing, inactive, non-author, and hidden-sector-only authors return a generic not-found error.

Agent View of the PolicyLayer registry record for `read_research_author`. HTML page: https://policylayer.com/tools/com-globalsourcepartners-emerging-markets-research/read-research-author

## Facts

- Tool: `read_research_author`
- 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: 1 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `author_uuid` | string | yes | The stable UUID of the research author to read. Use an author_uuid returned by another research tool. |

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": "read_research_author",
    "arguments": {
      "author_uuid": "<author_uuid>"
    }
  }
}
```

## Why read_research_author is rated Low

This tool retrieves and returns metadata about research authors without creating, modifying, deleting, executing code, or moving financial value. It is a straightforward read operation with minimal security risk—the worst case would be unauthorized exposure of public author profile information.

From the tool's own definition: "Tool name is 'read_research_author' with description stating it 'Read[s] a single research author' and 'returns author metadata, biography fields, profile URL, and visible sectors.' The verb 'read' and the retrieval of metadata with no modifications confirm…"

## Use case

AI agents call read_research_author 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": {
    "read_research_author": {}
  }
}
```

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

- `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
- `search_research_posts` — Read — https://policylayer.com/tools/com-globalsourcepartners-emerging-markets-research/search-research-posts.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