This record as markdown: /tools/io-github-2s-io-mcp/watchers.fear-greed.md
What watchers.fear-greed does on Mcp
AI agents use watchers.fear-greed to commit financial operations through Mcp, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why watchers.fear-greed is rated Critical
This tool involves a financial transaction — it charges USDC per invocation as part of the x402 pay-per-call mechanism. While the tool's primary function is a monitoring/read operation (watching the Fear & Greed index), every invocation commits a financial obligation (payment in USDC on Base or Solana). Per the rules, Financial outranks all other categories.
From the tool's definition pay-per-call tools settled in USDC on Base or Solana via x402... Arm once, pay once
Attacks that exploit this kind of access
The rule that runs watchers.fear-greed 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 watchers.fear-greed, this is the rule to start with:
Any call to watchers.fear-greed is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every watchers.fear-greed call is checked against it from then on.
Questions about watchers.fear-greed
WATCHER: get a signed callback when the Crypto Fear & Greed index crosses a level (e.g. drops into Extreme Fear). Arm once, pay once. conditionType \. It is categorised as a Financial tool in the Mcp MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the MCP server in PolicyLayer and add a rule for watchers.fear-greed: 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.
watchers.fear-greed is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the watchers.fear-greed 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 watchers.fear-greed. 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.
watchers.fear-greed 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