Execute an action on a target resource in AWS IoT SiteWise. This API executes an action on a target resource. Actions are typically used to bind computation models to specific assets or to trigger specific operations on resources. Args: action_definition_id: The ID of the action definition ...
Part of the AWS IoT SiteWise MCP Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents invoke execute_action to trigger processes or run actions in AWS IoT SiteWise MCP Server. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
execute_action can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
tools:
execute_action:
rules:
- action: allow
rate_limit:
max: 10
window: 60
validate:
required_args: trueSee the full AWS IoT SiteWise MCP Server policy for all 72 tools.
Agents calling execute-class tools like execute_action have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
execute_action is one of the high-risk operations in AWS IoT SiteWise MCP Server. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.
Execute an action on a target resource in AWS IoT SiteWise. This API executes an action on a target resource. Actions are typically used to bind computation models to specific assets or to trigger specific operations on resources. Args: action_definition_id: The ID of the action definition (required) action_payload: The JSON payload of the action containing stringValue (required) target_resource: The resource the action will be taken on (required) Must contain either assetId or computationModelId region: AWS region (default: us-east-1) client_token: Optional unique identifier for idempotent requests resolve_to: Optional detailed resource this action resolves to Must contain assetId if provided Returns: Dictionary containing the action execution response. Example: # Execute action on a computation model result = execute_action( action_definition_id='12345678-1234-1234-1234-123456789012', action_payload={'stringValue': '{"key": "value"}'}, target_resource={'computationModelId': '87654321-4321-4321-4321-210987654321'}, resolve_to={'assetId': '11111111-1111-1111-1111-111111111111'} ) # Execute action on an asset result = execute_action( action_definition_id='12345678-1234-1234-1234-123456789012', action_payload={'stringValue': '{"operation": "start"}'}, target_resource={'assetId': '87654321-4321-4321-4321-210987654321'} ). It is categorised as a Execute tool in the AWS IoT SiteWise MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Add a rule in your Intercept YAML policy under the tools section for execute_action. 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.
execute_action is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the execute_action 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 execute_action. 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.
execute_action 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.