Get recent tool call history.
AI agents call get_recent_tool_calls to retrieve information from TermPipe MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical data about previous tool invocations. It is a query/read operation that does not modify, execute, delete, or commit any resources. The low severity reflects that exposure of call history, while potentially informative to an attacker, does not directly enable harmful actions on its own. Confidence is high because the description unambiguously indicates a read-only retrieval function.
From the tool's definition Tool name is 'get_recent_tool_calls' and description states 'Get recent tool call history' — a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get recent tool call history. It is categorised as a Read tool in the TermPipe MCP MCP Server, which means it retrieves data without modifying state.
Register the TermPipe MCP server in PolicyLayer and add a rule for get_recent_tool_calls: 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 TermPipe MCP. Nothing to install.
get_recent_tool_calls 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_recent_tool_calls 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_recent_tool_calls. 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_recent_tool_calls is provided by the TermPipe MCP server (wbind-core/termpipe-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 →