list_dicom_import_jobs
AI agents call list_dicom_import_jobs to retrieve information from Awslabs Valkey without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears to retrieve or enumerate existing DICOM import job records without modifying, deleting, or executing operations. However, confidence is moderate (0.6) because the description is empty, making it impossible to confirm whether this tool could perform unintended actions like canceling jobs or accessing sensitive medical data. If it only lists job metadata, it remains a Read operation with low severity.
From the tool's definition Tool name 'list_dicom_import_jobs' indicates a query operation that lists or retrieves job status information. The absence of verbs like 'create', 'delete', 'execute', or 'modify' suggests read-only retrieval.
Attacks that exploit this kind of access
list_dicom_import_jobs. It is categorised as a Read tool in the Awslabs Valkey MCP Server, which means it retrieves data without modifying state.
Register the Awslabs Valkey MCP server in PolicyLayer and add a rule for list_dicom_import_jobs: 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 Awslabs Valkey. Nothing to install.
list_dicom_import_jobs 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 list_dicom_import_jobs 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 list_dicom_import_jobs. 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.
list_dicom_import_jobs is provided by the Awslabs Valkey MCP server (awslabs.valkey-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.