查看最近的命令执行历史，用于调试。
AI agents call get_history to retrieve information from Instrument MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays past command execution logs for debugging purposes. It performs a query-like operation on historical data with no capability to modify, delete, or execute new operations. The data retrieved is read-only and non-destructive.
From the tool's definition Tool name 'get_history' and description '查看最近的命令执行历史，用于调试' (view recent command execution history for debugging) indicate retrieval of historical data without modification or side effects.
Attacks that exploit this kind of access
查看最近的命令执行历史，用于调试。. It is categorised as a Read tool in the Instrument MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Instrument MCP Server MCP server in PolicyLayer and add a rule for get_history: 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 Instrument MCP Server. Nothing to install.
get_history 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 get_history 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 get_history. 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.
get_history is provided by the Instrument MCP Server MCP server (zeng-andrew/instrument-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 →