Create a new metadata transfer job for bulk import/export operations between S3 and IoT SiteWise. This tool provides a user-friendly way to set up metadata transfer jobs with support for bulk export using IoT SiteWise source configuration filters, avoiding the need for individual API calls. Arg...
High parameter count (11 properties)
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 create_metadata_transfer_job to initiate financial transactions through AWS IoT SiteWise MCP Server. Financial operations involve real money and are irreversible once processed. Intercept blocks financial tools by default, requiring explicit human approval with transaction-level limits to prevent unauthorised spending.
create_metadata_transfer_job moves real money. Without a policy, an autonomous agent could initiate transactions that drain accounts or exceed budgets. Intercept blocks financial tools by default, requiring human-in-the-loop approval with configurable spending limits per transaction and per time window.
Financial tools involve real money. Block by default and require explicit human approval before enabling.
tools:
create_metadata_transfer_job:
rules:
- action: deny
reason: "Requires human approval"See the full AWS IoT SiteWise MCP Server policy for all 72 tools.
Agents calling financial-class tools like create_metadata_transfer_job have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Financial risk category across the catalogue. The same policy patterns (deny, require_approval) apply to each.
create_metadata_transfer_job 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.
Create a new metadata transfer job for bulk import/export operations between S3 and IoT SiteWise. This tool provides a user-friendly way to set up metadata transfer jobs with support for bulk export using IoT SiteWise source configuration filters, avoiding the need for individual API calls. Args: transfer_direction: Direction of transfer: - "s3_to_sitewise": Import metadata from S3 to IoT SiteWise - "sitewise_to_s3": Export metadata from IoT SiteWise to S3 s3_bucket_name: S3 bucket name. If not provided, the agent should list available S3 buckets. s3_object_key: S3 object key/path. If not provided, will use sensible defaults. export_all_resources: For sitewise_to_s3: Export all IoT SiteWise resources using bulk filters asset_model_id: For sitewise_to_s3: Specific asset model ID to export asset_id: For sitewise_to_s3: Specific asset ID to export include_child_assets: For asset exports: Include child assets in hierarchy (includeOffspring). Cannot be True when include_asset_model is True. include_asset_model: For asset exports: Include asset model definition (includeAssetModel). Cannot be True when include_child_assets is True. region: AWS region (default: us-east-1) metadata_transfer_job_id: Optional custom job ID description: Optional job description Returns: Dictionary containing job creation response or guidance for next steps Examples: # Import from S3 to IoT SiteWise create_metadata_transfer_job( transfer_direction="s3_to_sitewise", s3_bucket_name="my-sitewise-metadata", s3_object_key="bulk-import/assets.json" ) # Export ALL IoT SiteWise resources to S3 (bulk export) create_metadata_transfer_job( transfer_direction="sitewise_to_s3", s3_bucket_name="my-sitewise-exports", export_all_resources=True ) # Export specific asset model and asset create_metadata_transfer_job( transfer_direction="sitewise_to_s3", s3_bucket_name="my-sitewise-exports", asset_model_id="a1b2c3d4-5678-90ab-cdef-1234567890ab", asset_id="f1e2d3c4-b5a6-9078-1234-567890abcdef" ). It is categorised as a Financial tool in the AWS IoT SiteWise MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Add a rule in your Intercept YAML policy under the tools section for create_metadata_transfer_job. 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.
create_metadata_transfer_job is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the create_metadata_transfer_job 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 create_metadata_transfer_job. 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.
create_metadata_transfer_job 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.