Vitally tool to search for accounts by multiple criteria
AI agents call search_accounts to retrieve information from Vitally 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 or queries account data based on specified criteria. Search operations are non-destructive reads that return information without side effects. The low severity reflects that misuse would only expose existing customer data rather than modify, delete, or trigger external actions. No financial or destructive operations are possible with a search function.
From the tool's definition Tool name 'search_accounts' and description 'search for accounts by multiple criteria' indicate a query operation with no modification, creation, or deletion of data.
Attacks that exploit this kind of access
Vitally tool to search for accounts by multiple criteria. It is categorised as a Read tool in the Vitally MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Vitally MCP Server MCP server in PolicyLayer and add a rule for search_accounts: 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 Vitally MCP Server. Nothing to install.
search_accounts 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 search_accounts 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 search_accounts. 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.
search_accounts is provided by the Vitally MCP Server MCP server (johnjjung/vitally-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 →