set_portfolio_context
Save your portfolio holdings so Fathom can give personalized guidance. Pass an array of holdings with asset name and amount. Example: [{asset:
This record as markdown: /tools/0xhashy-fathom-fyi/set-portfolio-context.md
What set_portfolio_context does on Fathom Fyi
AI agents use set_portfolio_context to create or update resources in Fathom Fyi, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Fathom Fyi environment.
Why set_portfolio_context is rated Medium
This tool creates or modifies portfolio data in Fathom's backend, making it a Write action. Severity is medium because while the direct action is reversible (holdings can be updated or cleared), misuse could lead to incorrect personalized financial guidance if an AI agent maliciously sets false holdings, potentially causing the user to make poor financial decisions based on bad context.
From the tool's definition Tool description states 'Save your portfolio holdings' — a persistent write operation that stores user portfolio data. The instruction to 'Pass an array of holdings with asset name and amount' confirms data creation/modification.
Attacks that exploit this kind of access
The rule that runs set_portfolio_context safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Fathom Fyi, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For set_portfolio_context, this is the rule to start with:
set_portfolio_context stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Fathom Fyi, apply this rule, and every set_portfolio_context call is checked against it from then on.
Questions about set_portfolio_context
Save your portfolio holdings so Fathom can give personalized guidance. Pass an array of holdings with asset name and amount. Example: [{asset:. It is categorised as a Write tool in the Fathom Fyi MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Fathom Fyi MCP server in PolicyLayer and add a rule for set_portfolio_context: 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 Fathom Fyi. Nothing to install.
set_portfolio_context is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the set_portfolio_context 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 set_portfolio_context. 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.
set_portfolio_context is provided by the Fathom Fyi MCP server (0xhashy/fathom-fyi). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Fathom Fyi, and thousands of servers like it.
This server
Across the catalogue