Get performance data for a Lighthouse portfolio
AI agents call getLighthousePerformanceData 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 portfolio performance metrics and historical data without creating, modifying, deleting, or executing external operations. While the data is financial in nature (crypto portfolio performance), the tool itself performs no financial transactions, only queries. The risk is limited to information disclosure, making it a Read category with low severity.
From the tool's definition Tool name 'getLighthousePerformanceData' and description 'Get performance data for a Lighthouse portfolio' indicate data retrieval only. The verb 'Get' and lack of modification language confirm read-only operations.
Attacks that exploit this kind of access
Get performance data for a Lighthouse portfolio. 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 getLighthousePerformanceData: 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.
getLighthousePerformanceData 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 getLighthousePerformanceData 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 getLighthousePerformanceData. 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.
getLighthousePerformanceData 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 →