Vitally tool to find an account by name (partial match supported)
AI agents call find_account_by_name 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 account information based on a name search. It performs a read-only lookup with no ability to modify, delete, or execute operations. The partial match search is a standard read operation. Severity is low because the blast radius of misuse is limited to exposing account names or IDs that are likely low-sensitivity metadata in a CRM context.
From the tool's definition Tool name 'find_account_by_name' and description 'find an account by name (partial match supported)' indicate a query/search operation with no modification or side effects.
Attacks that exploit this kind of access
Vitally tool to find an account by name (partial match supported). 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 find_account_by_name: 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.
find_account_by_name 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 find_account_by_name 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 find_account_by_name. 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.
find_account_by_name 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 →