Transfer cash between two Fidelity accounts. Validates available balance before submitting.
AI agents use fidelity_transfer to commit financial operations through Claude Fidelity — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool moves money between financial accounts, making it Financial category by definition. Severity is critical because an AI agent misusing this tool could instantly transfer funds without authorization, causing direct financial loss. The tool validates balances (a safeguard) but validation alone does not prevent misuse if the agent is instructed to transfer inappropriately.
From the tool's definition Tool explicitly 'Transfer[s] cash between two Fidelity accounts' and is part of a server that 'manages balances, positions, and trades' for brokerage accounts. Cash transfers directly commit financial obligations and move money between accounts.
Attacks that exploit this kind of access
Transfer cash between two Fidelity accounts. Validates available balance before submitting. It is categorised as a Financial tool in the Claude Fidelity MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Claude Fidelity MCP server in PolicyLayer and add a rule for fidelity_transfer: 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 Claude Fidelity. Nothing to install.
fidelity_transfer is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the fidelity_transfer 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 fidelity_transfer. 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.
fidelity_transfer is provided by the Claude Fidelity MCP server (tylerflar/claude-fidelity-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 →