# ecosystem_stats

Measured aggregates across the whole catalog: totals, maintainer count, license coverage, star concentration. Computed from harvested data, nothing estimated. Source: getagentictools.com/stats

Agent View of the PolicyLayer registry record for `ecosystem_stats`. HTML page: https://policylayer.com/tools/com-getagentictools-catalog/ecosystem-stats

## Facts

- Tool: `ecosystem_stats`
- Server: Catalog (`https://getagentictools.com/api/mcp`) — https://policylayer.com/tools/com-getagentictools-catalog.md
- Homepage: https://github.com/dmoka/getagentictools-mcp
- Risk category: Read (Low risk)
- Registry record: grade D, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

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

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

## Why ecosystem_stats is rated Low

This tool only reads and returns pre-computed aggregate statistics about the catalog ecosystem (totals, maintainer count, license coverage, star concentration). It has no capability to modify, create, delete, or execute external operations. It is a straightforward data retrieval operation with no side effects.

From the tool's own definition: "Tool description states it retrieves 'Measured aggregates' and 'Computed from harvested data' with no mention of modification, creation, deletion, or side effects. The name 'ecosystem_stats' and description align with querying/retrieving aggregate statistics."

## Use case

AI agents call ecosystem_stats to retrieve information from Catalog 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 Catalog:

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

## Other tools on Catalog (4)

- `get_tool` — Read — https://policylayer.com/tools/com-getagentictools-catalog/get-tool.md
- `list_categories` — Read — https://policylayer.com/tools/com-getagentictools-catalog/list-categories.md
- `search_tools` — Read — https://policylayer.com/tools/com-getagentictools-catalog/search-tools.md
- `whats_new` — Read — https://policylayer.com/tools/com-getagentictools-catalog/whats-new.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=com-getagentictools-catalog · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-getagentictools-catalog