get_historical_readings
AI agents call get_historical_readings to retrieve information from AC Infinity MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical data from AC Infinity controllers without creating, modifying, or deleting any resources. The empty description reduces confidence slightly, but the name and server context clearly indicate a read-only operation. Blast radius is minimal—an AI agent retrieving historical sensor data poses no safety or operational risk.
From the tool's definition Tool name 'get_historical_readings' indicates retrieval of past sensor data with no side effects. The server description confirms it is designed to 'read live sensor data' without modifying controller state.
Attacks that exploit this kind of access
get_historical_readings. It is categorised as a Read tool in the AC Infinity MCP MCP Server, which means it retrieves data without modifying state.
Register the AC Infinity MCP server in PolicyLayer and add a rule for get_historical_readings: 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 AC Infinity MCP. Nothing to install.
get_historical_readings 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_readings 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_readings. 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_readings is provided by the AC Infinity MCP server (ober37/ac-infinity-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 →