Get recent command-usage history.
AI agents call get_history_tool to retrieve information from Mcp Commands 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 records. It is purely informational—no data is created, modified, deleted, or executed. The blast radius of misuse is minimal; an attacker could only access historical metadata that has already been logged, not cause operational harm or data loss.
From the tool's definition Tool name 'get_history_tool' and description 'Get recent command-usage history' indicate a retrieval operation with no side effects. It queries historical data from the PostgreSQL database without modifying, deleting, or executing anything.
Attacks that exploit this kind of access
Get recent command-usage history. It is categorised as a Read tool in the Mcp Commands MCP Server, which means it retrieves data without modifying state.
Register the Mcp Commands MCP server in PolicyLayer and add a rule for get_history_tool: 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 Mcp Commands. Nothing to install.
get_history_tool 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_tool 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_tool. 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_tool is provided by the Mcp Commands MCP server (puemmth/mcp-commands). 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 →