getMarketEvents
Fetches upcoming cryptocurrency market events from CoinMarketCal (e.g. token launches, airdrops, listings, forks). Optionally filter by event category. Returns up to 50 events with dates, coins, proof links, and community votes.
This record as markdown: /tools/nanidao-agentek/getmarketevents.md
What getMarketEvents does on Agentek Eth
AI agents call getMarketEvents to retrieve information from Agentek Eth without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why getMarketEvents is rated Low
This tool retrieves publicly available market calendar data from CoinMarketCal without creating, modifying, executing, or deleting anything. It is a straightforward read operation with minimal security risk. An AI agent using this tool can only query event information, not alter market conditions, execute transactions, or perform destructive actions.
From the tool's definition Tool description states it 'Fetches upcoming cryptocurrency market events' and 'Returns up to 50 events with dates, coins, proof links, and community votes.' The verb 'Fetches' and 'Returns' indicate data retrieval with no modification or execution of…
Attacks that exploit this kind of access
The rule that runs getMarketEvents safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Agentek Eth, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For getMarketEvents, this is the rule to start with:
getMarketEvents 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 Agentek Eth, apply this rule, and every getMarketEvents call is checked against it from then on.
Questions about getMarketEvents
Fetches upcoming cryptocurrency market events from CoinMarketCal (e.g. token launches, airdrops, listings, forks). Optionally filter by event category. Returns up to 50 events with dates, coins, proof links, and community votes. It is categorised as a Read tool in the Agentek Eth MCP Server, which means it retrieves data without modifying state.
Register the Agentek Eth MCP server in PolicyLayer and add a rule for getMarketEvents: 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 Agentek Eth. Nothing to install.
getMarketEvents 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 getMarketEvents 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 getMarketEvents. 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.
getMarketEvents is provided by the Agentek Eth MCP server (nanidao/agentek). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Agentek Eth, and thousands of servers like it.
This server
Across the catalogue