verify_connection
AI agents call verify_connection 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 appears to verify or test a connection to a DICOM server without retrieving, modifying, or deleting data. This is consistent with a Read category operation—a simple diagnostic that returns connection status.
From the tool's definition Tool name 'verify_connection' indicates a diagnostic check to test connectivity to a DICOM server. Empty description limits clarity, but contextual inference from the server's purpose (querying DICOM systems) and sibling tools (all Read operations like…
Attacks that exploit this kind of access
verify_connection. 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 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 Simple Dicom. Nothing to install.
verify_connection 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 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.
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.
verify_connection 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 →