query_studies
AI agents call query_studies to retrieve information from Simple Dicom without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool queries DICOM studies data from medical imaging servers without indicating any modification, deletion, or execution capability. While querying sensitive medical data (healthcare records) carries inherent privacy risks, the tool itself performs passive retrieval only. Severity is low as the primary risk is information disclosure rather than system compromise or data loss.
From the tool's definition Tool name 'query_studies' combined with server context 'query and read data on DICOM servers' and sibling tools (query_instances, query_patients, query_series) all indicate read-only query operations.
Attacks that exploit this kind of access
query_studies. It is categorised as a Read tool in the Simple Dicom MCP Server, which means it retrieves data without modifying state.
Register the Simple Dicom MCP server in PolicyLayer and add a rule for query_studies: 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 Simple Dicom. Nothing to install.
query_studies 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_studies 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_studies. 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_studies is provided by the Simple Dicom MCP server (thalesmms/simple-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 →