Fetch the high-impact economic events calendar: CPI inflation releases, Non-Farm Payrolls (NFP), FOMC rate decisions, GDP prints, PMI data — with consensus forecasts vs prior values and market impact ratings. Use this tool when: - A trading agent needs to avoid holding positions through major dat...
AI agents call get_economic_calendar 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 data retrieval tool that queries a public economic calendar database. It provides informational signals (CPI, NFP, FOMC, GDP, PMI) that agents use for decision-making, but the tool itself performs no side effects. The server charges per call (x402 payment model), but the tool does not move funds or create financial obligations—payment is infrastructural, not a function of this tool.
From the tool's definition Tool fetches and returns economic calendar data (event_name, country, release_datetime_utc, impact ratings, consensus forecasts vs prior values).
Attacks that exploit this kind of access
Fetch the high-impact economic events calendar: CPI inflation releases, Non-Farm Payrolls (NFP), FOMC rate decisions, GDP prints, PMI data — with consensus forecasts vs prior values and market impact ratings. Use this tool when: - A trading agent needs to avoid holding positions through major data releases - A macro agent is building a weekly economic event schedule - You need to know the expected vs prior value for an upcoming release - An agent wants to assess whether upcoming events could move markets significantly Returns per event: event_name, country, release_datetime_utc, impact (HIGH/MEDIUM/LOW), forecast, previous, actual (if released), market_impact_assets. Example: getEconomicCalendar({ days: 7, 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_economic_calendar: 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_economic_calendar 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_economic_calendar 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_economic_calendar. 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_economic_calendar 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 →