List bulk import jobs in AWS IoT SiteWise. This function retrieves a paginated list of bulk import job summaries with optional filtering by job status. Each job summary includes basic information like job ID, name, status, and timestamps. Args: filter: Optional filter to apply to the list. ...
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 list_bulk_import_jobs 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 list_bulk_import_jobs 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:
list_bulk_import_jobs:
rules:
- action: allowSee the full AWS IoT SiteWise MCP Server policy for all 72 tools.
Agents calling read-class tools like list_bulk_import_jobs 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.
List bulk import jobs in AWS IoT SiteWise. This function retrieves a paginated list of bulk import job summaries with optional filtering by job status. Each job summary includes basic information like job ID, name, status, and timestamps. Args: filter: Optional filter to apply to the list. Valid values: - ALL: List all jobs (default) - PENDING: Jobs waiting to start - RUNNING: Jobs currently executing - CANCELLED: Jobs that were cancelled - FAILED: Jobs that failed - COMPLETED_WITH_FAILURES: Jobs completed but with some failures - COMPLETED: Jobs that completed successfully next_token: Token for paginated results max_results: Maximum number of results to return (1-250, default: 25) region: AWS region (default: us-east-1) Returns: Dictionary containing: - success: Boolean indicating operation success - job_summaries: List of job summary objects - next_token: Token for next page (if applicable) Example: # List all bulk import jobs result = list_bulk_import_jobs() # List only running jobs result = list_bulk_import_jobs(filter="RUNNING") # List with pagination result = list_bulk_import_jobs(max_results=10, next_token="..."). 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 list_bulk_import_jobs. 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.
list_bulk_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_bulk_import_jobs 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 list_bulk_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_bulk_import_jobs 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.