Critical Risk →

delete_asset

Delete an asset. Args: asset_id: The ID of the asset to delete. Accepts UUID format (12345678-1234-1234-1234-123456789012) or external ID format (externalId:my-external-id). Use list_assets to get the correct ID if you only have the asset name. region: AWS regio...

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

AI agents may call delete_asset to permanently remove or destroy resources in AWS IoT SiteWise MCP Server. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. Intercept blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call delete_asset in a loop, permanently destroying resources in AWS IoT SiteWise MCP Server. There is no undo for destructive operations. Intercept blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

aws-iot-sitewise-mcp-server.yaml
tools:
  delete_asset:
    rules:
      - action: deny
        reason: "Blocked by default — enable with approval"

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

Tool Name delete_asset
Category Destructive
Risk Level Critical

View all 72 tools →

Agents calling destructive-class tools like delete_asset 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 Destructive risk category across the catalogue. The same policy patterns (deny, require_approval) apply to each.

delete_asset is one of the critical-risk operations in AWS IoT SiteWise MCP Server. For the full severity-focused view — only the critical-risk tools with their recommended policies — see the breakdown for this server, or browse all critical-risk tools across every MCP server.

What does the delete_asset tool do? +

Delete an asset. Args: asset_id: The ID of the asset to delete. Accepts UUID format (12345678-1234-1234-1234-123456789012) or external ID format (externalId:my-external-id). Use list_assets to get the correct ID if you only have the asset name. region: AWS region (default: us-east-1) client_token: A unique case-sensitive identifier for the request Returns: Dictionary containing deletion response. It is categorised as a Destructive tool in the AWS IoT SiteWise MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_asset? +

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

delete_asset is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_asset? +

Yes. Add a rate_limit block to the delete_asset 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 delete_asset completely? +

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

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