Get a specific FRED economic indicator with historical observations. WHEN TO USE: For detailed history of one indicator. Use veroq_economy (no args) for a summary of all indicators. RETURNS: Series info (ID, frequency, units), latest value, and historical observations array. COST: 2 credits. EXAM...
AI agents call veroq_economy_indicator 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 is a data retrieval tool that queries public economic indicator data. It has no side effects, cannot modify data, execute code, or affect financial transactions. While the server overall provides financial intelligence, this specific tool merely fetches and returns historical economic statistics without the ability to place trades, move money, or alter any state.
From the tool's definition Tool retrieves historical economic indicator data from FRED with 'Get a specific FRED economic indicator with historical observations.' No modification, deletion, or execution capabilities described.
Attacks that exploit this kind of access
Get a specific FRED economic indicator with historical observations. WHEN TO USE: For detailed history of one indicator. Use veroq_economy (no args) for a summary of all indicators. RETURNS: Series info (ID, frequency, units), latest value, and historical observations array. 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_indicator: 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_indicator 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_indicator 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_indicator. 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_indicator 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 →