Get vault staking event history.
AI agents call get_vault_events to retrieve information from Basis MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical event data from vault staking operations. It performs a read-only query with no side effects, no state changes, and no ability to modify, delete, or execute operations. The low severity reflects minimal blast radius—an AI agent misusing this tool could only access potentially sensitive staking history information, not cause financial loss or system compromise.
From the tool's definition Tool name 'get_vault_events' and description 'Get vault staking event history' indicate data retrieval with 'Get' verb and 'event history' implies querying historical records without modification.
Attacks that exploit this kind of access
Get vault staking event history. It is categorised as a Read tool in the Basis MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Basis MCP Server MCP server in PolicyLayer and add a rule for get_vault_events: 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 Basis MCP Server. Nothing to install.
get_vault_events 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_vault_events 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_vault_events. 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_vault_events is provided by the Basis MCP Server MCP server (launch-on-basis/mcp-ts). 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 →