Fetch macroeconomic fundamentals for major economies: central bank interest rates, CPI inflation, M2 money supply, unemployment, GDP growth, yield curve shape, and G10 FX rates. Returns a rate_environment signal (HAWKISH/DOVISH/NEUTRAL). Use this tool when: - An agent needs to understand the glob...
AI agents call get_macro_data 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 pure read operation that retrieves publicly available macroeconomic data and derives a signal classification. While the data is valuable for financial decision-making, the tool itself performs no writes, executions, destructive actions, or financial transactions.
From the tool's definition Tool description indicates data retrieval only: 'Fetch macroeconomic fundamentals' and 'Returns a rate_environment signal'. No mutations, deletions, code execution, or financial transactions are performed.
Attacks that exploit this kind of access
Fetch macroeconomic fundamentals for major economies: central bank interest rates, CPI inflation, M2 money supply, unemployment, GDP growth, yield curve shape, and G10 FX rates. Returns a rate_environment signal (HAWKISH/DOVISH/NEUTRAL). Use this tool when: - An agent needs to understand the global interest rate environment before making investment decisions - A macro-aware trading agent wants to align trades with the dominant monetary policy regime - You need to assess inflation trends and their impact on asset classes - A portfolio agent wants to know which economies are expanding or contracting Returns per country: policy_rate, CPI_yoy, M2_growth, unemployment_rate, GDP_growth_qoq, yield_curve (2y-10y spread), currency_vs_usd, rate_environment_signal. Example: getMacroData({ countries:. 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_macro_data: 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_macro_data 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_macro_data 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_macro_data. 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_macro_data 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 →