# maiga_market_report

Generates specialized market reports based on different analysis modes

Agent View of the PolicyLayer registry record for `maiga_market_report`. HTML page: https://policylayer.com/tools/demomagic-lucy-maiga-mcp/maiga-market-report

## Facts

- Tool: `maiga_market_report`
- Server: Maiga (`demomagic/lucy-maiga-mcp`) — https://policylayer.com/tools/demomagic-lucy-maiga-mcp.md
- Homepage: https://github.com/demomagic/lucy-maiga-mcp
- Risk category: Read (Low risk)
- Registry record: grade A, identity unverified
- Server rate-limited: no
- Parameters: 1
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `mode` | string | no | Analysis mode: Market_Behavior, Open_Interest, Multi_Timeframe, or Fund_Flow |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "maiga_market_report",
    "arguments": {}
  }
}
```

## Why maiga_market_report is rated Low

This tool retrieves, aggregates, and presents market analysis information about cryptocurrency tokens. Generating reports from existing data is a Read operation with no side effects. No data is created, modified, deleted, or financial transactions are executed. The blast radius of misuse is limited to potential misinformation from a report, but the tool itself performs no irreversible actions or financial operations.

From the tool's own definition: "Tool description states it 'Generates specialized market reports' - a report generation function that retrieves and synthesizes existing analysis data without modifying state. Named 'market_report' indicating informational output."

## Use case

AI agents call maiga_market_report to retrieve information from Maiga without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Maiga:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "maiga_market_report": {}
  }
}
```

## Other tools on Maiga (5)

- `maiga_analyse_token` — Read — https://policylayer.com/tools/demomagic-lucy-maiga-mcp/maiga-analyse-token.md
- `maiga_kol_analysis` — Read — https://policylayer.com/tools/demomagic-lucy-maiga-mcp/maiga-kol-analysis.md
- `maiga_mindshare` — Read — https://policylayer.com/tools/demomagic-lucy-maiga-mcp/maiga-mindshare.md
- `maiga_token_info` — Read — https://policylayer.com/tools/demomagic-lucy-maiga-mcp/maiga-token-info.md
- `maiga_trending_tokens` — Read — https://policylayer.com/tools/demomagic-lucy-maiga-mcp/maiga-trending-tokens.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=demomagic-lucy-maiga-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/demomagic-lucy-maiga-mcp