AI agents call get_historical_data to retrieve information from Ambient without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical weather data from personal weather stations with no apparent side effects. The tool follows a read-only naming convention consistent with other data-fetching tools on the server. Empty description slightly reduces confidence, but the context is clear enough to classify as a Read operation with low blast radius if misused.
From the tool's definition Tool name 'get_historical_data' and server context (Ambient Weather REST API) indicate data retrieval. Description is empty, but the name and sibling tools (get_devices, get_latest_observation) suggest a read-only query pattern.
Attacks that exploit this kind of access
get_historical_data. It is categorised as a Read tool in the Ambient MCP Server, which means it retrieves data without modifying state.
Register the Ambient MCP server in PolicyLayer and add a rule for get_historical_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 Ambient. Nothing to install.
get_historical_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_historical_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_historical_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_historical_data is provided by the Ambient MCP server (jrolstad/ambient-mcp). 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 →