verify_connection · DICOM MCP Server MCP: Risk & Policy

WHAT IT DOES

What verify_connection does on DICOM MCP Server

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

WHY IT NEEDS A POLICY

Why verify_connection needs a policy

Verification checks typically read system status without modifying data or executing external operations. No side effects expected. Classified as Read rather than Other due to clear naming and server context, despite the empty description lowering confidence from 0.85 to 0.75.

From the tool's definition Tool name 'verify_connection' suggests a diagnostic check to test connectivity to DICOM servers. Empty description limits certainty, but the name and server context (querying/reading medical imaging data) indicate this likely performs a non-destructive test…

Attacks that exploit this kind of access

Questions about verify_connection

What does the verify_connection tool do? +

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

How do I enforce a policy on verify_connection? +

Register the DICOM MCP Server MCP server in PolicyLayer and add a rule for verify_connection: 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.

What risk level is verify_connection? +

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

Can I rate-limit verify_connection? +

Yes. Add a rate_limit block to the verify_connection 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 verify_connection completely? +

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

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