Get the history of an asset property's values. Args: asset_id: The ID of the asset property_id: The ID of the asset property property_alias: The alias that identifies the property start_date: The exclusive start of the range (ISO 8601 format) end_date: The inclusive end of th...
High parameter count (10 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 call get_asset_property_value_history to retrieve information from AWS IoT SiteWise MCP Server without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though get_asset_property_value_history only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
get_asset_property_value_history:
rules:
- action: allowSee the full AWS IoT SiteWise MCP Server policy for all 72 tools.
Agents calling read-class tools like get_asset_property_value_history have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Get the history of an asset property's values. Args: asset_id: The ID of the asset property_id: The ID of the asset property property_alias: The alias that identifies the property start_date: The exclusive start of the range (ISO 8601 format) end_date: The inclusive end of the range (ISO 8601 format) qualities: The quality by which to filter asset data (GOOD, BAD, UNCERTAIN) time_ordering: The chronological sorting order of the requested information (ASCENDING, DESCENDING) next_token: The token to be used for the next set of paginated results max_results: The maximum number of results to return (1-4000, default: 100) region: AWS region (default: us-east-1) Returns: Dictionary containing property value history. It is categorised as a Read tool in the AWS IoT SiteWise MCP Server MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for get_asset_property_value_history. 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.
get_asset_property_value_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_asset_property_value_history 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 get_asset_property_value_history. 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.
get_asset_property_value_history 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.