Get history of interruptions for debugging and analysis.
AI agents call get_interruption_history to retrieve information from Session Buddy without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries historical data about interruptions for debugging purposes. It is a straightforward read operation that retrieves information without creating, modifying, deleting, or executing any code. The purpose is purely informational—to understand what interruptions occurred in past sessions. This poses minimal security risk as it only exposes diagnostic metadata.
From the tool's definition Tool name 'get_interruption_history' and description 'Get history of interruptions for debugging and analysis' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get history of interruptions for debugging and analysis. It is categorised as a Read tool in the Session Buddy MCP Server, which means it retrieves data without modifying state.
Register the Session Buddy MCP server in PolicyLayer and add a rule for get_interruption_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 Session Buddy. Nothing to install.
get_interruption_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_interruption_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_interruption_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_interruption_history is provided by the Session Buddy MCP server (lesleslie/session-buddy). 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 →