AI agents call get_event_impact to retrieve information from Curistat without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs retrospective analysis of past economic events and their volatility effects. It queries historical information to inform decision-making but does not execute trades, modify market data, create positions, or trigger external operations. Even in an AI trading context, misuse would result in poor analysis rather than unintended financial transactions or system compromise.
From the tool's definition The tool name 'get_event_impact' and description 'Analyze historical volatility impact of a specific economic event' indicate a query operation that retrieves and analyzes historical data without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
Analyze historical volatility impact of a specific economic event. It is categorised as a Read tool in the Curistat MCP Server, which means it retrieves data without modifying state.
Register the Curistat MCP server in PolicyLayer and add a rule for get_event_impact: 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 Curistat. Nothing to install.
get_event_impact 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_event_impact 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_event_impact. 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_event_impact is provided by the Curistat MCP server (moxiespirit/curistat-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 →