econ.recession
Composite US recession-signal dashboard: NY Fed recession probability (12mo ahead), Sahm-rule real-time indicator (≥0.50 = recession begun), and 10y2y Treasury spread (negative = inverted). Each with value, date, triggered flag, and a count of signals flashing. A read of the standard gauges, not ...
This record as markdown: /tools/io-github-2s-io-mcp/econ.recession.md
What econ.recession does on Mcp
AI agents call econ.recession to retrieve information from Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why econ.recession is rated Low
This tool queries and retrieves financial/economic data without any capability to modify, delete, execute code, or move money. It aggregates publicly available recession indicators into a dashboard format. The 'read-only' nature is explicitly confirmed in the description.
From the tool's definition Tool description explicitly states it is 'A read of the standard gauges, not a forecast' and retrieves composite data (NY Fed recession probability, Sahm-rule indicator, Treasury spread) from FRED.
Attacks that exploit this kind of access
The rule that runs econ.recession safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For econ.recession, this is the rule to start with:
econ.recession is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every econ.recession call is checked against it from then on.
Questions about econ.recession
Composite US recession-signal dashboard: NY Fed recession probability (12mo ahead), Sahm-rule real-time indicator (≥0.50 = recession begun), and 10y2y Treasury spread (negative = inverted). Each with value, date, triggered flag, and a count of signals flashing. A read of the standard gauges, not a forecast. Source: FRED. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
Register the MCP server in PolicyLayer and add a rule for econ.recession: 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 Mcp. Nothing to install.
econ.recession 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 econ.recession 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 econ.recession. 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.
econ.recession is provided by the MCP server (@2sio/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on , and thousands of servers like it.
This server
Across the catalogue