switch_dicom_node
AI agents use switch_dicom_node 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.
Based on the tool name, it likely changes the active/target DICOM node (PACS/VNA server) being used. This is a configuration change (Write category) that could redirect data queries or transfers to a different medical imaging server. Severity is medium because misconfiguration could cause data to be sent to or retrieved from an unintended endpoint. Confidence is low due to empty description.
From the tool's definition Tool name 'switch_dicom_node'; description is empty and uninformative.
Attacks that exploit this kind of access
switch_dicom_node. 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 switch_dicom_node: 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.
switch_dicom_node 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 switch_dicom_node 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 switch_dicom_node. 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.
switch_dicom_node 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.
switch_dicom_node is one line of DICOM MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →