move_study
AI agents use move_study to create or update resources in DICOM MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your DICOM MCP Server environment.
Moving studies in a DICOM system transfers medical imaging data between locations (e.g., PACS, VNA, or external endpoints). This is a Write operation because it modifies the data's location state reversibly. Severity is high because medical imaging data is sensitive (PHI/PII under HIPAA), and unauthorized movement could expose patient information, violate compliance, or disrupt clinical workflows.
From the tool's definition Tool name 'move_study' combined with sibling tool 'move_series' and server description stating the tool enables 'image transfer to AI endpoints'. The 'move_' prefix indicates data relocation/transfer rather than retrieval.
Attacks that exploit this kind of access
move_study. It is categorised as a Write tool in the DICOM MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the DICOM MCP Server MCP server in PolicyLayer and add a rule for move_study: 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_study 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 move_study 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_study. 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_study 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 →