ims_list_open_sessions
AI agents call ims_list_open_sessions to retrieve information from IMS MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool lists open sessions—a query operation that retrieves state information without side effects. It does not create, modify, delete, or execute anything. The confidence is slightly below 1.0 only because the tool description is empty, requiring inference from the name and server context alone, but the 'list' verb and session-management context provide strong signals for Read classification.
From the tool's definition Tool name 'ims_list_open_sessions' uses 'list' verb, which retrieves or enumerates existing sessions without modification. The server description emphasizes 'session management' and 'memory storage' capabilities.
Attacks that exploit this kind of access
ims_list_open_sessions. It is categorised as a Read tool in the IMS MCP Server MCP Server, which means it retrieves data without modifying state.
Register the IMS MCP Server MCP server in PolicyLayer and add a rule for ims_list_open_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 IMS MCP Server. Nothing to install.
ims_list_open_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 ims_list_open_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 ims_list_open_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.
ims_list_open_sessions is provided by the IMS MCP Server MCP server (jdelon02/ims-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 →