AI agents call check_release_calendar to retrieve information from Econstats without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only reads/queries economic calendar data to determine if a release day has occurred. It performs no modifications, executions, deletions, or financial transactions. The purpose is informational guidance for subsequent data retrieval decisions. Low severity reflects that misuse cannot cause harm beyond retrieving stale or outdated calendar information.
From the tool's definition Tool description states it 'Check[s] if today is a major economic data release day' — a query/lookup operation with no side effects. The tool retrieves calendar information to inform which data source to use, similar to a calendar lookup or status check.
Attacks that exploit this kind of access
Check if today is a major economic data release day (jobs, CPI, GDP, etc). If yes, use BLS/BEA direct instead of FRED. It is categorised as a Read tool in the Econstats MCP Server, which means it retrieves data without modifying state.
Register the Econstats MCP server in PolicyLayer and add a rule for check_release_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 Econstats. Nothing to install.
check_release_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 check_release_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 check_release_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.
check_release_calendar is provided by the Econstats MCP server (joshfwaldman1/econstats-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 →