crypto_market_signal
Paid (x402, $0.005 USDC on Base). For each CoinGecko id return price, market cap, 24h change, 24h volume, plus a derived momentum score (-100..100), a bullish/neutral/bearish signal, and a volatility flag — enriched data an agent ingests in a trading/research loop.
This record as markdown: /tools/dev-charliemorrison-agent-web-reader/crypto-market-signal.md
What crypto_market_signal does on Agent Web Reader
AI agents call crypto_market_signal to retrieve information from Agent Web Reader without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
ids | string | Yes | Comma-separated CoinGecko ids (e.g. 'bitcoin,ethereum,solana'), max 25 |
x402_payment | string | — | Base64 X-PAYMENT header from your x402 wallet (omit to get the payment challenge) |
Parameters from the server's own tool schema.
Why crypto_market_signal is rated Low
The tool fetches and enriches cryptocurrency market data (price, volume, momentum, signals) for ingestion in a trading/research loop. It does not itself execute trades or move funds.
From the tool's definition 'return price, market cap, 24h change, 24h volume, plus a derived momentum score, a bullish/neutral/bearish signal' — retrieves and enriches market data; no trade execution described
Attacks that exploit this kind of access
The rule that runs crypto_market_signal safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Agent Web Reader, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For crypto_market_signal, this is the rule to start with:
crypto_market_signal 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 Agent Web Reader, apply this rule, and every crypto_market_signal call is checked against it from then on.
Questions about crypto_market_signal
Paid (x402, $0.005 USDC on Base). For each CoinGecko id return price, market cap, 24h change, 24h volume, plus a derived momentum score (-100..100), a bullish/neutral/bearish signal, and a volatility flag — enriched data an agent ingests in a trading/research loop. It is categorised as a Read tool in the Agent Web Reader MCP Server, which means it retrieves data without modifying state.
crypto_market_signal accepts 2 parameters: ids, x402_payment. Required: ids. The full parameter table on this page comes from the server's own tool schema.
Register the Agent Web Reader MCP server in PolicyLayer and add a rule for crypto_market_signal: 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 Agent Web Reader. Nothing to install.
crypto_market_signal 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 crypto_market_signal 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 crypto_market_signal. 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.
crypto_market_signal is provided by the Agent Web Reader MCP server (https://x402.charliemorrison.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Agent Web Reader, and thousands of servers like it.
This server
Across the catalogue