# get_operator_memoirs

根据干员名称查询干员密录剧情。

Agent View of the PolicyLayer registry record for `get_operator_memoirs`. HTML page: https://policylayer.com/tools/3akhp-prts-mcp/get-operator-memoirs

## Facts

- Tool: `get_operator_memoirs`
- Server: Prts (`3akhp/prts-mcp`) — https://policylayer.com/tools/3akhp-prts-mcp.md
- Homepage: https://github.com/3aKHP/prts-mcp
- Risk category: Read (Low risk)
- Registry record: grade A, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

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

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_operator_memoirs",
    "arguments": {}
  }
}
```

## Why get_operator_memoirs is rated Low

This tool retrieves operator memoir storylines from the PRTS Wiki API based on a character name parameter. It is purely informational—reading and returning narrative content from game lore. There are no side effects, state changes, or irreversible actions. The confidence is high because the consistent naming pattern and server design (fan-creation AI agents needing lore) clearly indicate read-only data access.

From the tool's own definition: "Tool description states it queries (查询) operator memoirs/stories by operator name. The verb 'get_' prefix combined with 'query' indicates data retrieval only."

## Use case

AI agents call get_operator_memoirs to retrieve information from Prts 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 Prts:

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

## Other tools on Prts (10)

- `find_character_appearances` — Read — https://policylayer.com/tools/3akhp-prts-mcp/find-character-appearances.md
- `find_speakers_in` — Read — https://policylayer.com/tools/3akhp-prts-mcp/find-speakers-in.md
- `get_story_summary` — Read — https://policylayer.com/tools/3akhp-prts-mcp/get-story-summary.md
- `list_stories` — Read — https://policylayer.com/tools/3akhp-prts-mcp/list-stories.md
- `list_story_events` — Read — https://policylayer.com/tools/3akhp-prts-mcp/list-story-events.md
- `prts_page` — Read — https://policylayer.com/tools/3akhp-prts-mcp/prts-page.md
- `read_activity` — Read — https://policylayer.com/tools/3akhp-prts-mcp/read-activity.md
- `read_story` — Read — https://policylayer.com/tools/3akhp-prts-mcp/read-story.md
- `search_prts` — Read — https://policylayer.com/tools/3akhp-prts-mcp/search-prts.md
- `search_stories` — Read — https://policylayer.com/tools/3akhp-prts-mcp/search-stories.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=3akhp-prts-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/3akhp-prts-mcp