Fetch Wall Street analyst upgrades and downgrades: firm name, rating change, new price target, and implied upside/downside from current price. Use this tool when: - A trading agent wants to know if a stock has recently been upgraded or downgraded - You need analyst price targets to assess consens...
AI agents call get_analyst_ratings to retrieve information from Omni Service Node without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a Read operation: it queries and retrieves analyst data without side effects. However, severity is elevated to 'medium' rather than 'low' because the tool operates in a financial intelligence context on a pay-per-call service (x402 USDC-gated), and output directly informs trading decisions.
From the tool's definition Tool fetches and retrieves Wall Street analyst ratings, upgrades, downgrades, price targets, and implied upside/downside—descriptive fields only. No modification, deletion, or financial transaction occurs.
Attacks that exploit this kind of access
Fetch Wall Street analyst upgrades and downgrades: firm name, rating change, new price target, and implied upside/downside from current price. Use this tool when: - A trading agent wants to know if a stock has recently been upgraded or downgraded - You need analyst price targets to assess consensus valuation - A research agent is tracking sentiment changes at major investment banks - An agent wants to identify contrarian signals (mass downgrades = potential bottoms) Returns: ticker, company, analyst_firm, old_rating, new_rating, old_target, new_target, implied_upside_pct, date, analyst_name. Example: getAnalystRatings({ symbol:. It is categorised as a Read tool in the Omni Service Node MCP Server, which means it retrieves data without modifying state.
Register the Omni Service Node MCP server in PolicyLayer and add a rule for get_analyst_ratings: 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 Omni Service Node. Nothing to install.
get_analyst_ratings 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_analyst_ratings 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_analyst_ratings. 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_analyst_ratings is provided by the Omni Service Node MCP server (luckkyyy23/omni-service-node). 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 →