list_dicom_export_jobs
AI agents call list_dicom_export_jobs to retrieve information from AWS IoT SiteWise MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'list_' prefix is a standard pattern for retrieval operations that query existing data without side effects. Even in the context of AWS IoT SiteWise (which may handle medical imaging data via DICOM format), listing export jobs is a non-destructive read operation. No write, execute, destructive, or financial operations are implied.
From the tool's definition Tool name 'list_dicom_export_jobs' indicates a listing/querying operation with the verb 'list', which retrieves information about export jobs without modifying data. The description is empty, but the naming convention strongly suggests a read-only operation.
Attacks that exploit this kind of access
list_dicom_export_jobs. It is categorised as a Read tool in the AWS IoT SiteWise MCP Server MCP Server, which means it retrieves data without modifying state.
Register the AWS IoT SiteWise MCP Server MCP server in PolicyLayer and add a rule for list_dicom_export_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 AWS IoT SiteWise MCP Server. Nothing to install.
list_dicom_export_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_export_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_export_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_export_jobs is provided by the AWS IoT SiteWise MCP Server MCP server (awslabs.aws-iot-sitewise-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.