get_dicom_export_job
AI agents call get_dicom_export_job 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 'get' prefix strongly suggests a read operation that retrieves or queries data about a DICOM export job without modifying it. However, confidence is reduced due to the empty description—we cannot definitively rule out side effects (e.g., triggering an export or state change) that might make this Execute.
From the tool's definition Tool name 'get_dicom_export_job' uses the 'get' verb, indicating retrieval of information about a DICOM export job status or details. No description provided to confirm scope.
Attacks that exploit this kind of access
get_dicom_export_job. 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 get_dicom_export_job: 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.
get_dicom_export_job 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 get_dicom_export_job 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 get_dicom_export_job. 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.
get_dicom_export_job 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.