Get detailed information about a specific bulk import job in AWS IoT SiteWise. This function retrieves comprehensive details about a bulk import job including its configuration, status, progress, error information, and execution statistics. Args: job_id: The unique identifier of the bulk im...
Single-target operation
Part of the AWS IoT SiteWise MCP Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call describe_bulk_import_job to retrieve information from AWS IoT SiteWise MCP Server without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though describe_bulk_import_job only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
describe_bulk_import_job:
rules:
- action: allowSee the full AWS IoT SiteWise MCP Server policy for all 72 tools.
Agents calling read-class tools like describe_bulk_import_job have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Get detailed information about a specific bulk import job in AWS IoT SiteWise. This function retrieves comprehensive details about a bulk import job including its configuration, status, progress, error information, and execution statistics. Args: job_id: The unique identifier of the bulk import job (UUID format) region: AWS region (default: us-east-1) Returns: Dictionary containing: - success: Boolean indicating operation success - job_id: The job identifier - job_name: The job name - job_status: Current status of the job - job_role_arn: IAM role ARN used by the job - files: List of input files - error_report_location: S3 location for error reports - job_configuration: Job configuration details - job_creation_date: When the job was created - job_last_update_date: When the job was last updated - adaptive_ingestion: Whether adaptive ingestion is enabled - delete_files_after_import: Whether files are deleted after import - Additional fields based on job status and execution Example: # Get details for a specific job result = describe_bulk_import_job( job_id="12345678-1234-1234-1234-123456789012" ) if result['success']: print(f"Job Status: {result['job_status']}") print(f"Job Name: {result['job_name']}"). It is categorised as a Read tool in the AWS IoT SiteWise MCP Server MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for describe_bulk_import_job. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the AWS IoT SiteWise MCP Server MCP server.
describe_bulk_import_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 describe_bulk_import_job rule in your Intercept 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 Intercept policy for describe_bulk_import_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.
describe_bulk_import_job is provided by the AWS IoT SiteWise MCP Server MCP server (awslabs.aws-iot-sitewise-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.