Medium Risk

update_asset_model

Update an asset model. Args: asset_model_id: The ID of the asset model to update. Accepts UUID format (12345678-1234-1234-1234-123456789012) or external ID format (externalId:my-external-id). Use list_asset_models to get the correct ID if you only have t...

Part of the AWS IoT SiteWise MCP Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents use update_asset_model to create or modify resources in AWS IoT SiteWise MCP Server. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call update_asset_model repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach AWS IoT SiteWise MCP Server.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

aws-iot-sitewise-mcp-server.yaml
tools:
  update_asset_model:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full AWS IoT SiteWise MCP Server policy for all 72 tools.

Tool Name update_asset_model
Category Write
Risk Level Medium

View all 72 tools →

Agents calling write-class tools like update_asset_model have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

What does the update_asset_model tool do? +

Update an asset model. Args: asset_model_id: The ID of the asset model to update. Accepts UUID format (12345678-1234-1234-1234-123456789012) or external ID format (externalId:my-external-id). Use list_asset_models to get the correct ID if you only have the asset model name. asset_model_name: A unique, friendly name for the asset model region: AWS region (default: us-east-1) asset_model_description: A description for the asset model asset_model_properties: The updated property definitions of the asset model asset_model_hierarchies: The updated hierarchy definitions of the asset model asset_model_composite_models: The updated composite models client_token: A unique case-sensitive identifier for the request asset_model_external_id: An external ID to assign to the asset model Returns: Dictionary containing update response. It is categorised as a Write tool in the AWS IoT SiteWise MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_asset_model? +

Add a rule in your Intercept YAML policy under the tools section for update_asset_model. 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.

What risk level is update_asset_model? +

update_asset_model is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_asset_model? +

Yes. Add a rate_limit block to the update_asset_model 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.

How do I block update_asset_model completely? +

Set action: deny in the Intercept policy for update_asset_model. 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.

What MCP server provides update_asset_model? +

update_asset_model 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.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.