Lists interactsh sessions cached in memory.
AI agents call list_interactsh_sessions to retrieve information from MCP Interactsh Bridge without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and enumerates existing interactsh sessions from local memory cache. It performs no data modification, deletion, or external operations—purely informational read access. While the context involves security testing infrastructure, the tool itself has minimal blast radius as it only exposes session metadata already within the agent's operational scope.
From the tool's definition Tool name 'list_interactsh_sessions' and description 'Lists interactsh sessions cached in memory' indicate a query/retrieval operation with no modification of data.
Attacks that exploit this kind of access
Lists interactsh sessions cached in memory. It is categorised as a Read tool in the MCP Interactsh Bridge MCP Server, which means it retrieves data without modifying state.
Register the MCP Interactsh Bridge MCP server in PolicyLayer and add a rule for list_interactsh_sessions: 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 Interactsh Bridge. Nothing to install.
list_interactsh_sessions 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 list_interactsh_sessions 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 list_interactsh_sessions. 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.
list_interactsh_sessions is provided by the MCP Interactsh Bridge MCP server (tachote/mcp-interactsh). 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 →