ims_wrap_session
AI agents call ims_wrap_session as a supporting operation in IMS MCP Server workflows.
The description is entirely empty, making it impossible to determine exactly what this tool does. Based on the name 'wrap_session', it may finalize or close a session, which could be a Write or Execute operation, but without evidence I cannot confidently assign a more severe category. Confidence is low due to the lack of description.
From the tool's definition Tool name is 'ims_wrap_session'; description is empty or uninformative.
Attacks that exploit this kind of access
ims_wrap_session. It is categorised as a Other tool in the IMS MCP Server MCP Server, which means it performs auxiliary operations.
Register the IMS MCP Server MCP server in PolicyLayer and add a rule for ims_wrap_session: 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_wrap_session is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the ims_wrap_session 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_wrap_session. 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_wrap_session 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 →