move_series
AI agents invoke move_series to trigger actions in DICOM MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
DICOM C-MOVE operations trigger active data transfer between nodes on the network. The tool description is empty, but by analogy with the sibling 'move_study' and the server description's mention of 'image transfer to AI endpoints', this tool initiates an external network operation (C-MOVE) that causes a remote DICOM node to push data to a destination AE.
From the tool's definition Tool name 'move_series' on a DICOM MCP server that 'move[s] medical imaging data' and transfers images 'to AI endpoints for analysis'; sibling tool 'move_study' confirms the pattern of DICOM C-MOVE operations.
Attacks that exploit this kind of access
move_series. It is categorised as a Execute tool in the DICOM MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the DICOM MCP Server MCP server in PolicyLayer and add a rule for move_series: 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 DICOM MCP Server. Nothing to install.
move_series is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the move_series 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 move_series. 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.
move_series is provided by the DICOM MCP Server MCP server (y5ive9ine/dicom-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 →