List executions for a specific target resource in AWS IoT SiteWise. Retrieves a paginated list of executions that occurred after performing execute actions on the specified target resource. This shows the progress status, error information, and execution details for training actions, inference s...
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 list_executions 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_executions 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_executions:
rules:
- action: allowSee the full AWS IoT SiteWise MCP Server policy for all 72 tools.
Agents calling read-class tools like list_executions 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 executions for a specific target resource in AWS IoT SiteWise. Retrieves a paginated list of executions that occurred after performing execute actions on the specified target resource. This shows the progress status, error information, and execution details for training actions, inference schedules, and other action types. Args: target_resource_id: The ID of the target resource to list executions for (required, must be in UUID format) target_resource_type: The type of resource - ASSET or COMPUTATION_MODEL (required) region: AWS region (default: us-east-1) action_type: Optional type of action executed to filter results max_results: Optional maximum number of results to return (1-250) next_token: Optional token for pagination to get the next set of results resolve_to_resource_id: Optional ID of the resolved resource resolve_to_resource_type: Optional type of the resolved resource (ASSET) Returns: Dictionary containing the list of executions and pagination info. Example: # List all executions for a computation model result = list_executions( target_resource_id='12345678-1234-1234-1234-123456789012', target_resource_type='COMPUTATION_MODEL' ) # List executions for an asset with pagination result = list_executions( target_resource_id='87654321-4321-4321-4321-210987654321', target_resource_type='ASSET', max_results=50 ) # List executions filtered by action type result = list_executions( target_resource_id='12345678-1234-1234-1234-123456789012', target_resource_type='COMPUTATION_MODEL', action_type='AWS/ANOMALY_DETECTION_TRAINING' ) # List executions resolved to a specific asset result = list_executions( target_resource_id='12345678-1234-1234-1234-123456789012', target_resource_type='COMPUTATION_MODEL', resolve_to_resource_id='11111111-1111-1111-1111-111111111111', resolve_to_resource_type='ASSET' ) # Get next page of results result = list_executions( target_resource_id='12345678-1234-1234-1234-123456789012', target_resource_type='COMPUTATION_MODEL', next_token=previous_result['nextToken'] ). 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_executions. 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_executions 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_executions 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_executions. 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_executions 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.