fidelity_submit_2fa · Claude Fidelity MCP: Risk & Policy

WHAT IT DOES

What fidelity_submit_2fa does on Claude Fidelity

AI agents invoke fidelity_submit_2fa to trigger actions in Claude Fidelity. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why fidelity_submit_2fa needs a policy

This tool submits a 2FA authentication code via browser automation to complete login to a financial brokerage account. While the immediate action is executing an authentication step (not directly moving money), it enables access to a Fidelity investment account with trading capabilities.

From the tool's definition Submit the SMS 2FA code received on your phone to complete Fidelity login

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

fidelity_submit_2fa Rate-limited

fidelity_submit_2fa stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "fidelity_submit_2fa": {
      "limits": [
        {
          "counter": "fidelity_submit_2fa_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Claude Fidelity, so you can run agents against it safely.

FAQ

Questions about fidelity_submit_2fa

What does the fidelity_submit_2fa tool do? +

Submit the SMS 2FA code received on your phone to complete Fidelity login. Only use this after fidelity_login returns needsSms2FA=true. It is categorised as a Execute tool in the Claude Fidelity MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on fidelity_submit_2fa? +

Register the Claude Fidelity MCP server in PolicyLayer and add a rule for fidelity_submit_2fa: 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.

What risk level is fidelity_submit_2fa? +

fidelity_submit_2fa is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit fidelity_submit_2fa? +

Yes. Add a rate_limit block to the fidelity_submit_2fa 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.

How do I block fidelity_submit_2fa completely? +

Set action: deny in the PolicyLayer policy for fidelity_submit_2fa. 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.

What MCP server provides fidelity_submit_2fa? +

fidelity_submit_2fa 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.