history

Show edit history for this session.

Server TermPipe MCP wbind-core/termpipe-mcp
Category Read
Risk class Low
Parameters 00 required

What history does on TermPipe MCP

AI agents call history 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.

Why history needs a policy

The tool reads and displays the edit history for the current session. It is a read-only retrieval operation with no ability to modify, execute, or delete anything. However, the broader server context (terminal access, command execution) is high-risk, and history data could expose sensitive commands previously run, slightly elevating concern but not the category.

From the tool's definition 'Show edit history for this session' — retrieves historical data with no side effects

Questions about history

What does the history tool do? +

Show edit history for this session. It is categorised as a Read tool in the TermPipe MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on history? +

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

What risk level is history? +

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

Can I rate-limit history? +

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

How do I block history completely? +

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

What MCP server provides history? +

history 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.