get_historical_data
AI agents call get_historical_data to retrieve information from Aareguru MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves historical data about the Aare river with no side effects. Even though the description is empty, the function name and server context clearly indicate a read-only query operation. There is no evidence of data modification, deletion, or execution of arbitrary operations. The checkout-related siblings are in a separate functional domain.
From the tool's definition Tool name 'get_historical_data' indicates data retrieval. The server provides river monitoring data (temperature, flow rates, forecasts) with no modification or deletion capabilities described.
Attacks that exploit this kind of access
get_historical_data. It is categorised as a Read tool in the Aareguru MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Aareguru MCP Server 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 Aareguru MCP Server. 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 Aareguru MCP Server MCP server (schlpbch/aareguru-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 →