oe_history_list

List question history from OpenEvidence account.

SERVER: SOURCEhtlin222/openevidence-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade C, identity unverified Pull the record →

This record as markdown: /tools/htlin222-openevidence-mcp/oe-history-list.md

WHAT IT DOES

What oe_history_list does on :

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.

RISK

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 definition oe_history_list is described as 'List question history from OpenEvidence account', which retrieves historical data without modifying or deleting it.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs oe_history_list safely

PolicyLayer is an MCP gateway: it sits between your AI agents and :, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For oe_history_list, this is the rule to start with:

oe_history_list Allowed

oe_history_list is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect :, apply this rule, and every oe_history_list call is checked against it from then on.

FAQ

Questions about oe_history_list

What does the oe_history_list tool do? +

List question history from OpenEvidence account. It is categorised as a Read tool in the : MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on oe_history_list? +

Register the : MCP server in PolicyLayer and add a rule for oe_history_list: 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 :. Nothing to install.

What risk level is oe_history_list? +

oe_history_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit oe_history_list? +

Yes. Add a rate_limit block to the oe_history_list 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.

How do I block oe_history_list completely? +

Set action: deny in the PolicyLayer policy for oe_history_list. 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.

What MCP server provides oe_history_list? +

oe_history_list is provided by the : MCP server (htlin222/openevidence-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on :, and thousands of servers like it.

This server

All 19 : tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →