query_studies
AI agents call query_studies 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 queries DICOM study records without modifying them. While the description is empty (reducing confidence slightly), the semantic context—'query' operations, medical imaging metadata retrieval, and sibling query tools—clearly positions this as a data retrieval function.
From the tool's definition Tool name 'query_studies' combined with sibling tools like 'query_patients' and 'query_series' that are explicitly described as querying/searching operations. Server description states the tool enables 'query' and 'read' of medical imaging data.
Attacks that exploit this kind of access
query_studies. 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_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 DICOM MCP Server. 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 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 →