get_historical_data
AI agents call get_historical_data to retrieve information from Crypto Pegmon without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name strongly suggests querying historical cryptocurrency or stablecoin data, which is a read-only operation with no side effects. Even with an empty description, the naming pattern and server context (crypto analysis tools) indicate data retrieval rather than modification, execution, or deletion.
From the tool's definition Tool name 'get_historical_data' indicates data retrieval. Description is empty, reducing confidence. Context from sibling tools (analyze_peg_stability, get_current_price, get_supported_stablecoins) suggests this server retrieves cryptocurrency/stablecoin…
Attacks that exploit this kind of access
get_historical_data. It is categorised as a Read tool in the Crypto Pegmon MCP Server, which means it retrieves data without modifying state.
Register the Crypto Pegmon 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 Crypto Pegmon. 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 Crypto Pegmon MCP server (kukapay/crypto-pegmon-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 →