Fetch and display a detailed summary of a Lighthouse portfolio with breakdown by asset types and major holdings.
AI agents call getLighthousePortfolio to retrieve information from Lighthouse MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays portfolio data without creating, modifying, deleting, executing code, or moving funds. It is a straightforward query operation with no side effects. While it accesses financial information, the tool itself performs no financial transactions or commitments. The main risk is unauthorized data access, which is mitigated by the 'secure authentication' mentioned in the server description.
From the tool's definition Tool name is 'getLighthousePortfolio' and description states 'Fetch and display a detailed summary' — both indicate data retrieval without modification.
Attacks that exploit this kind of access
Fetch and display a detailed summary of a Lighthouse portfolio with breakdown by asset types and major holdings. It is categorised as a Read tool in the Lighthouse MCP MCP Server, which means it retrieves data without modifying state.
Register the Lighthouse MCP server in PolicyLayer and add a rule for getLighthousePortfolio: 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 Lighthouse MCP. Nothing to install.
getLighthousePortfolio 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 getLighthousePortfolio 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 getLighthousePortfolio. 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.
getLighthousePortfolio is provided by the Lighthouse MCP server (l3wi/mcp-lighthouse). 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 →