query_patients
AI agents call query_patients to retrieve information from DICOM 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 patient information from DICOM servers without modifying or deleting data. However, it accesses highly sensitive Protected Health Information (PHI) in medical imaging systems, warranting high severity due to privacy risks and compliance implications (HIPAA).
From the tool's definition Tool name 'query_patients' indicates patient data retrieval. Server description confirms it enables 'patient searches' and 'query, read, download' of medical imaging data on DICOM servers (PACS, VNA).
Attacks that exploit this kind of access
query_patients. It is categorised as a Read tool in the DICOM MCP Server MCP Server, which means it retrieves data without modifying state.
Register the DICOM MCP Server MCP server in PolicyLayer and add a rule for query_patients: 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.
query_patients 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 query_patients 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 query_patients. 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.
query_patients 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 →