查询设备属性点的历史时序数据
AI agents call get_history_data to retrieve information from AIRIOT MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical time series data from IoT devices without creating, modifying, deleting, or executing operations. It is a passive read operation with no side effects, falling clearly under the Read category with low severity risk.
From the tool's definition Tool name 'get_history_data' and description '查询设备属性点的历史时序数据' (query device property point historical time series data) indicates data retrieval only. The verb '查询' means 'query/retrieve' with no modification or deletion capability.
Attacks that exploit this kind of access
查询设备属性点的历史时序数据. It is categorised as a Read tool in the AIRIOT MCP Server MCP Server, which means it retrieves data without modifying state.
Register the AIRIOT MCP Server MCP server in PolicyLayer and add a rule for get_history_data: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches AIRIOT MCP Server. Nothing to install.
get_history_data 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_history_data rule in your PolicyLayer 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 PolicyLayer policy for get_history_data. 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_history_data is provided by the AIRIOT MCP Server MCP server (sshwsfc/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →