# directory_stats

Aggregate statistics across devrel.directory in one call: listing counts by category; active job count, distinct hiring companies, the workplace mix (remote/hybrid/onsite counts), the share of roles that are remote or remote-friendly (the site's own classification, which also reads remote-prefixed locations), and salary min/median/max computed ONLY over roles stating USD pay (currencies are never blended); upcoming event count, open CFPs, and CFPs closing within 30 days. Every salary figure carries n, the number of disclosing roles - always cite n alongside any salary figure, and treat a small n as a weak signal; smallSample is true when that sample is below the threshold the site itself requires before quoting a headline salary, so qualify the figures rather than repeating them flat. Each section carries a canonicalUrl to the devrel.directory page behind it, and methodologyUrl links the page stating how the salary figures are computed.

Agent View of the PolicyLayer registry record for `directory_stats`. HTML page: https://policylayer.com/tools/directory-devrel-devrel-directory/directory-stats

## Facts

- Tool: `directory_stats`
- Server: DevRel Directory (`https://devrel.directory/mcp`) — https://policylayer.com/tools/directory-devrel-devrel-directory.md
- Homepage: https://github.com/https://devrel.directory/mcp
- Risk category: Read (Low risk)
- Registry record: grade C, 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": "directory_stats",
    "arguments": {}
  }
}
```

## Why directory_stats is rated Low

Even though directory_stats only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Risk signals: Bulk/mass operation — affects multiple targets

## Use case

AI agents call directory_stats to retrieve information from DevRel Directory 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 DevRel Directory:

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

## Other tools on DevRel Directory (5)

- `get_listing` — Read — https://policylayer.com/tools/directory-devrel-devrel-directory/get-listing.md
- `list_events` — Read — https://policylayer.com/tools/directory-devrel-devrel-directory/list-events.md
- `list_jobs` — Read — https://policylayer.com/tools/directory-devrel-devrel-directory/list-jobs.md
- `search_directory` — Read — https://policylayer.com/tools/directory-devrel-devrel-directory/search-directory.md
- `search_docs` — Read — https://policylayer.com/tools/directory-devrel-devrel-directory/search-docs.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=directory-devrel-devrel-directory · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/directory-devrel-devrel-directory