Low Risk

rsu_sell_vs_hold

After-tax payout on a Restricted Stock Unit (RSU) vest: federal ordinary income tax, state income tax, FICA (Social Security + Medicare + Additional Medicare), and the gap between mandatory 22% federal supplemental withholding and the user's marginal bracket. Use this tool for RSUs at vest; for I...

Risk signalsHigh parameter count (11 properties) · Bulk/mass operation — affects multiple targets

Part of the Optionsahoy Mcp server.

rsu_sell_vs_hold is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE OPTIONSAHOY MCP →

Free to start. No card required.

AI agents call rsu_sell_vs_hold to retrieve information from Optionsahoy Mcp without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though rsu_sell_vs_hold only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "rsu_sell_vs_hold": {}
  }
}

See the full Optionsahoy Mcp policy for all 7 tools.

Get this rule live on your own Optionsahoy Mcp server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY OPTIONSAHOY MCP →

These attack patterns abuse exactly the kind of access rsu_sell_vs_hold gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so rsu_sell_vs_hold only ever does what you allow.

SECURE OPTIONSAHOY MCP →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the rsu_sell_vs_hold tool do? +

After-tax payout on a Restricted Stock Unit (RSU) vest: federal ordinary income tax, state income tax, FICA (Social Security + Medicare + Additional Medicare), and the gap between mandatory 22% federal supplemental withholding and the user's marginal bracket. Use this tool for RSUs at vest; for ISO/AMT planning use amt_iso_optimize, for NSO use nso_calculate. Compares sell-at-vest vs hold-for-long-term-capital-gains (LTCG) across the chosen horizon, accounting for the 12-month short-term-vs-long-term holding threshold and the optional expected-growth assumption. Pure deterministic computation: no network access; tax tables and the 22% supplemental-withholding rate are compiled in. Returns a top-level object with keys: vest (vestValue, federal, state, socialSecurity, medicare, additionalMedicare, total, netCashAtVest, federalWithheldAtVest), hold (expectedGain at horizon, capGainFederal/State/Total including NIIT, isLongTerm), sellNowInvest (counterfactual: sell at vest and reinvest at expectedMarketReturn), holdMinusSell (dollar delta), and bracketJump (fromRate, toRate, thresholdAtJump on the vest amount). Example call: {shares: 1000, currentPrice: 100, ordinaryIncome: 200000, filingStatus: "single", stateCode: "CA", stillEmployed: true, holdYears: 2, volatility: 0.3, ticker: "MSFT"}. IMPORTANT: every field listed in required must come from the user's message OR be derivable from an optional ticker. The model invoking this tool MUST NOT invent a value for any required field. If the user did not supply it and no ticker resolves it, ask the user.. It is categorised as a Read tool in the Optionsahoy Mcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on rsu_sell_vs_hold? +

Register the Optionsahoy MCP server in PolicyLayer and add a rule for rsu_sell_vs_hold: 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 Optionsahoy Mcp. Nothing to install.

What risk level is rsu_sell_vs_hold? +

rsu_sell_vs_hold is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit rsu_sell_vs_hold? +

Yes. Add a rate_limit block to the rsu_sell_vs_hold 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 rsu_sell_vs_hold completely? +

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

rsu_sell_vs_hold is provided by the Optionsahoy MCP server (https://optionsahoy.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Optionsahoy Mcp tool call.

Deterministic rules across all 7 Optionsahoy Mcp tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.