Directory of financial accounts (existence, ownership, beneficiary, last4). Does NOT track balances — those come from live integrations.
AI agents call financial_accounts to retrieve information from Personal Brain without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves sensitive personal financial metadata (account ownership, beneficiary information, partial account numbers) but performs no modifications, deletions, or financial transactions. It is clearly a Read operation.
From the tool's definition Tool description explicitly states it provides a "Directory of financial accounts (existence, ownership, beneficiary, last4)" with no write, delete, or financial transaction capabilities.
Attacks that exploit this kind of access
Directory of financial accounts (existence, ownership, beneficiary, last4). Does NOT track balances — those come from live integrations. It is categorised as a Read tool in the Personal Brain MCP Server, which means it retrieves data without modifying state.
Register the Personal Brain MCP server in PolicyLayer and add a rule for financial_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 Personal Brain. Nothing to install.
financial_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 financial_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 financial_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.
financial_accounts is provided by the Personal Brain MCP server (phantomts/personal-brain-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 →