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-prefixe...
This record as markdown: /tools/directory-devrel-devrel-directory/directory-stats.md
What directory_stats does on DevRel Directory
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.
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 signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs directory_stats safely
PolicyLayer is an MCP gateway: it sits between your AI agents and DevRel Directory, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For directory_stats, this is the rule to start with:
directory_stats 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 DevRel Directory, apply this rule, and every directory_stats call is checked against it from then on.
Questions about 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. It is categorised as a Read tool in the DevRel Directory MCP Server, which means it retrieves data without modifying state.
Register the DevRel Directory MCP server in PolicyLayer and add a rule for directory_stats: 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 DevRel Directory. Nothing to install.
directory_stats 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 directory_stats 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 directory_stats. 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.
directory_stats is provided by the DevRel Directory MCP server (https://devrel.directory/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on DevRel Directory, and thousands of servers like it.
This server
Across the catalogue