get_portfolio_alerts
AI agents call get_portfolio_alerts to retrieve information from Financial MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get_' prefix and sibling tool patterns (check_stock_alerts) indicate this is a read operation that retrieves existing portfolio alert information. No modification, deletion, or financial transaction occurs. The empty description reduces confidence but context clues strongly suggest data retrieval. Classified as Read with low severity due to information disclosure only.
From the tool's definition Tool name 'get_portfolio_alerts' contains 'get', which indicates a retrieval operation. Description is empty, limiting confidence.
Attacks that exploit this kind of access
get_portfolio_alerts. It is categorised as a Read tool in the Financial MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Financial MCP Server MCP server in PolicyLayer and add a rule for get_portfolio_alerts: 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 Financial MCP Server. Nothing to install.
get_portfolio_alerts 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 get_portfolio_alerts 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 get_portfolio_alerts. 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.
get_portfolio_alerts is provided by the Financial MCP Server MCP server (osamadev/financial_mcp_server). 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 →