查询中国历史事件的详细信息,包括事件背景、经过、影响等。
AI agents call history_event_query to retrieve information from Unified MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves historical information. It performs a read-only operation that returns data about Chinese historical events without modifying, deleting, or executing any external systems. There is no financial impact, code execution, or destructive capability. The blast radius of misuse is minimal—an agent could only retrieve unwanted historical information.
From the tool's definition Tool name 'history_event_query' and description '查询中国历史事件的详细信息,包括事件背景、经过、影响等' (Query detailed information about Chinese historical events, including event background, process, and impact) indicates a retrieval/query operation with no side effects.
Attacks that exploit this kind of access
查询中国历史事件的详细信息,包括事件背景、经过、影响等。. It is categorised as a Read tool in the Unified MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Unified MCP Server MCP server in PolicyLayer and add a rule for history_event_query: 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 Unified MCP Server. Nothing to install.
history_event_query is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the history_event_query 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.
Set action: deny in the PolicyLayer policy for history_event_query. 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.
history_event_query is provided by the Unified MCP Server MCP server (qingyunyupan/ollama-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →