query_instances

query_instances

Server Simple Dicom thalesmms/simple-dicom-mcp
Category Read
Risk class Low
Parameters 00 required

What query_instances does on Simple Dicom

AI agents call query_instances 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.

Why query_instances needs a policy

The tool name 'query_instances' and its context within a DICOM querying suite strongly suggests it retrieves medical imaging instance data. While the description is empty (lowering confidence slightly), the sibling tools and server purpose leave little doubt this is a Read operation.

From the tool's definition Tool is part of a DICOM server query system alongside query_patients, query_series, and query_studies, all of which are Read operations.

Questions about query_instances

What does the query_instances tool do? +

query_instances. It is categorised as a Read tool in the Simple Dicom MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on query_instances? +

Register the Simple Dicom MCP server in PolicyLayer and add a rule for query_instances: 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.

What risk level is query_instances? +

query_instances is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit query_instances? +

Yes. Add a rate_limit block to the query_instances 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.

How do I block query_instances completely? +

Set action: deny in the PolicyLayer policy for query_instances. 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.

What MCP server provides query_instances? +

query_instances 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.