AI agents call aevo_get_status 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.
This is a read-only operation that queries the current status and identity context. It has no side effects, does not execute trades, modify accounts, or delete data. The tool simply returns information about the MCP runtime state and AEVO authentication context, making it a straightforward information retrieval function with minimal risk.
From the tool's definition Tool name 'aevo_get_status' and description 'Return MCP runtime and AEVO identity context' indicate it retrieves status information and context data without modifying or executing any operations.
Attacks that exploit this kind of access
Return MCP runtime and AEVO identity context. 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_status: 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_status 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_status 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_status. 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_status 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 →