Get macroeconomic indicators from FRED. No arguments returns a summary of all key indicators; pass a slug for detailed history. WHEN TO USE: For macro data like GDP, CPI, unemployment, fed funds rate. Use veroq_economy_indicator for a single indicator with history. RETURNS: Summary mode: all indi...
AI agents call veroq_economy to retrieve information from Veroq without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries macroeconomic data from FRED (Federal Reserve Economic Data). It performs no mutations, deletions, or side effects—purely data retrieval. No financial transactions, code execution, or destructive operations are involved. This is a straightforward Read operation with minimal blast radius if misused.
From the tool's definition Get macroeconomic indicators from FRED. No arguments returns a summary of all key indicators; pass a slug for detailed history. Returns summary or series data with historical observations.
Attacks that exploit this kind of access
Get macroeconomic indicators from FRED. No arguments returns a summary of all key indicators; pass a slug for detailed history. WHEN TO USE: For macro data like GDP, CPI, unemployment, fed funds rate. Use veroq_economy_indicator for a single indicator with history. RETURNS: Summary mode: all indicators with latest values. Detail mode: series info, latest value, and historical observations. COST: 2 credits. EXAMPLE: {. It is categorised as a Read tool in the Veroq MCP Server, which means it retrieves data without modifying state.
Register the Veroq MCP server in PolicyLayer and add a rule for veroq_economy: 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 Veroq. Nothing to install.
veroq_economy 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 veroq_economy 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 veroq_economy. 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.
veroq_economy is provided by the Veroq MCP server (veroq-ai/veroq-mcp). 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 →