AI agents call aevo_get_mark_history to retrieve information from Aevo-MCP 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 retrieving mark price history (historical market data), which is a read-only query operation with no side effects. The empty description limits confidence slightly, but the 'get_' prefix and context of a trading platform API indicates data retrieval rather than modification or execution. Read operations on financial data have low blast radius if misused by an agent.
From the tool's definition Tool name 'aevo_get_mark_history' indicates a retrieval operation ('get') with 'history' suggesting historical data query.
Attacks that exploit this kind of access
aevo_get_mark_history. It is categorised as a Read tool in the Aevo-MCP MCP Server, which means it retrieves data without modifying state.
Register the Aevo- MCP server in PolicyLayer and add a rule for aevo_get_mark_history: 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 Aevo-MCP. Nothing to install.
aevo_get_mark_history 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 aevo_get_mark_history 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 aevo_get_mark_history. 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.
aevo_get_mark_history is provided by the Aevo- MCP server (ribbon-finance/aevo-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 →