Describe an execution in AWS IoT SiteWise. Retrieves detailed information about a specific execution, including execution details, status, timestamps, target resource information, and execution results. This provides comprehensive information about the execution process. Args: execution_id:...
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_execution 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_execution 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_execution:
rules:
- action: allowSee the full AWS IoT SiteWise MCP Server policy for all 72 tools.
Agents calling read-class tools like describe_execution 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.
Describe an execution in AWS IoT SiteWise. Retrieves detailed information about a specific execution, including execution details, status, timestamps, target resource information, and execution results. This provides comprehensive information about the execution process. Args: execution_id: The ID of the execution to describe (required) region: AWS region (default: us-east-1) Returns: Dictionary containing the execution details. Example: # Describe a specific execution result = describe_execution('87654321-4321-4321-4321-210987654321') # The response includes: # - executionId: The ID of the execution # - actionType: The type of action executed # - executionStatus: Current status with state information # - executionStartTime: When the execution started (Unix timestamp) # - executionEndTime: When the execution completed (Unix timestamp, if finished) # - executionDetails: Detailed information about the execution (key-value pairs) # - executionResult: The result of the execution (key-value pairs) # - targetResource: The resource the action was taken on # - resolveTo: The detailed resource this execution resolves to (if applicable) # - executionEntityVersion: Entity version used for the execution # - targetResourceVersion: Version of the target resource. 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_execution. 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_execution 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_execution 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_execution. 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_execution 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.