# oe_history_list

List question history from OpenEvidence account.

Agent View of the PolicyLayer registry record for `oe_history_list`. HTML page: https://policylayer.com/tools/htlin222-openevidence-mcp/oe-history-list

## Facts

- Tool: `oe_history_list`
- Server: : (`htlin222/openevidence-mcp`) — https://policylayer.com/tools/htlin222-openevidence-mcp.md
- Homepage: https://github.com/htlin222/openevidence-mcp
- Risk category: Read (Low risk)
- Registry record: grade C, 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": "oe_history_list",
    "arguments": {}
  }
}
```

## Why oe_history_list is rated Low

This tool simply retrieves and displays question history—a query operation with no side effects. It falls squarely into the Read category. Severity is low because exposing query results to historical questions poses minimal risk unless the history contains highly sensitive information, which is not indicated. The confidence is high due to the clear read-only nature of the operation.

From the tool's own definition: "oe_history_list is described as 'List question history from OpenEvidence account', which retrieves historical data without modifying or deleting it."

## Use case

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

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

## Other tools on : (18)

- `oe_collections_sync_db` — Destructive — https://policylayer.com/tools/htlin222-openevidence-mcp/oe-collections-sync-db.md
- `oe_answers_search` — Read — https://policylayer.com/tools/htlin222-openevidence-mcp/oe-answers-search.md
- `oe_article_get` — Read — https://policylayer.com/tools/htlin222-openevidence-mcp/oe-article-get.md
- `oe_auth_status` — Read — https://policylayer.com/tools/htlin222-openevidence-mcp/oe-auth-status.md
- `oe_collections_classify` — Read — https://policylayer.com/tools/htlin222-openevidence-mcp/oe-collections-classify.md
- `oe_collections_get` — Read — https://policylayer.com/tools/htlin222-openevidence-mcp/oe-collections-get.md
- `oe_collections_list` — Read — https://policylayer.com/tools/htlin222-openevidence-mcp/oe-collections-list.md
- `oe_collections_summary` — Read — https://policylayer.com/tools/htlin222-openevidence-mcp/oe-collections-summary.md
- `oe_collections_unsorted` — Read — https://policylayer.com/tools/htlin222-openevidence-mcp/oe-collections-unsorted.md
- `oe_health` — Read — https://policylayer.com/tools/htlin222-openevidence-mcp/oe-health.md
- `oe_public_get` — Read — https://policylayer.com/tools/htlin222-openevidence-mcp/oe-public-get.md
- `oe_article_set_access` — Write — https://policylayer.com/tools/htlin222-openevidence-mcp/oe-article-set-access.md
- `oe_ask` — Write — https://policylayer.com/tools/htlin222-openevidence-mcp/oe-ask.md
- `oe_collections_add_article` — Write — https://policylayer.com/tools/htlin222-openevidence-mcp/oe-collections-add-article.md
- `oe_collections_bulk_apply` — Write — https://policylayer.com/tools/htlin222-openevidence-mcp/oe-collections-bulk-apply.md
- `oe_collections_create` — Write — https://policylayer.com/tools/htlin222-openevidence-mcp/oe-collections-create.md
- `oe_collections_db_init` — Write — https://policylayer.com/tools/htlin222-openevidence-mcp/oe-collections-db-init.md
- `oe_collections_sync_history` — Write — https://policylayer.com/tools/htlin222-openevidence-mcp/oe-collections-sync-history.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=htlin222-openevidence-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/htlin222-openevidence-mcp