Configure storage settings for AWS IoT SiteWise. Args: storage_type: The storage tier that you specified for your data ( SITEWISE_DEFAULT_STORAGE, MULTI_LAYER_STORAGE) region: AWS region (default: us-east-1) multi_layer_storage: Identifies a storage destination disassocia...
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 put_storage_configuration 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 put_storage_configuration 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.
tools:
put_storage_configuration:
rules:
- action: allow
rate_limit:
max: 30
window: 60See the full AWS IoT SiteWise MCP Server policy for all 72 tools.
Agents calling write-class tools like put_storage_configuration have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
Configure storage settings for AWS IoT SiteWise. Args: storage_type: The storage tier that you specified for your data ( SITEWISE_DEFAULT_STORAGE, MULTI_LAYER_STORAGE) region: AWS region (default: us-east-1) multi_layer_storage: Identifies a storage destination disassociated_data_storage: Contains the storage configuration for time series data that isn't associated with asset properties retention_period: How many days your data is kept in the hot tier warm_tier: A service managed storage tier optimized for analytical queries (ENABLED, DISABLED) warm_tier_retention_period: Set this period to specify how long your data is stored in the warm tier Returns: Dictionary containing storage configuration 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.
Add a rule in your Intercept YAML policy under the tools section for put_storage_configuration. 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.
put_storage_configuration is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the put_storage_configuration 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 put_storage_configuration. 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.
put_storage_configuration 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.