US consumer-demand signal - the demand-side mirror of CyclePulse. Returns headline retail & food-services sales with month/year trend, the core measure (excluding autos and gasoline - the cleaner underlying-demand read), e-commerce vs restaurant spending, a 13-sector year-over-year breakdown with...
AI agents call consumer_pulse to retrieve information from Mcp Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
consumer_pulse is a data retrieval tool that queries and returns US consumer demand statistics and economic indicators. The verb 'Returns' and the focus on reading/analyzing economic metrics (sales figures, spending patterns, trend analysis) confirms this is a Read operation. There are no side effects, no data modification, no code execution, and no financial operations.
From the tool's definition Tool description states it 'Returns headline retail & food-services sales', 'e-commerce vs restaurant spending', 'year-over-year breakdown', and provides 'plain-English consumer phase' analysis.
Attacks that exploit this kind of access
US consumer-demand signal - the demand-side mirror of CyclePulse. Returns headline retail & food-services sales with month/year trend, the core measure (excluding autos and gasoline - the cleaner underlying-demand read), e-commerce vs restaurant spending, a 13-sector year-over-year breakdown with strongest/weakest movers, and a plain-English consumer phase (resilient, softening, stalling, or pullback). Use it to read whether the US consumer is accelerating or cooling and gauge discretionary demand. Values are nominal (not inflation-adjusted). Companion to CyclePulse (supply) and macro data. Source: US Census Advance Retail Trade (MARTS), public domain. Monthly release. $0.05 via x402. It is categorised as a Read tool in the Mcp Server MCP Server, which means it retrieves data without modifying state.
Register the Mcp Server MCP server in PolicyLayer and add a rule for consumer_pulse: 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 Server. Nothing to install.
consumer_pulse 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 consumer_pulse 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 consumer_pulse. 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.
consumer_pulse is provided by the Mcp Server MCP server (Homie4570/lso-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
consumer_pulse is one line of Mcp Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →