handoff_create
AI agents use handoff_create to create or update resources in IMS MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your IMS MCP Server environment.
The 'create' verb combined with the IMS context (session management, memory storage) indicates this tool creates new records or handoff artifacts in the system. This is a Write operation—reversible data creation. Without evidence of deletion, financial impact, or code execution, and given the sibling tools are all 'create' operations on a memory/graph system, Write is the appropriate category.
From the tool's definition Tool name 'handoff_create' suggests creating a handoff record or session transfer artifact. The server description mentions 'session management' and 'memory storage', and sibling tools include 'graph_create_*' operations which are clearly Write-category.
Attacks that exploit this kind of access
handoff_create. It is categorised as a Write tool in the IMS MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the IMS MCP Server MCP server in PolicyLayer and add a rule for handoff_create: 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.
handoff_create is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the handoff_create 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 handoff_create. 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.
handoff_create 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 →