Get the IMS session currently bound to a hook session id.
AI agents call ims_get_bound_session 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 retrieves session information associated with a given session ID. It performs a query operation that returns existing data without creating, modifying, deleting, or executing any operations. The verb 'Get' combined with the read-only nature of session lookup classifies this as a Read operation.
From the tool's definition Tool name 'ims_get_bound_session' and description 'Get the IMS session currently bound to a hook session id' indicate a retrieval operation with no modification or deletion of data.
Attacks that exploit this kind of access
Get the IMS session currently bound to a hook session id. 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_get_bound_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_get_bound_session 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_get_bound_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_get_bound_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_get_bound_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 →