get_listing
Get the full detail for one directory listing by its slug, including longer details when present, the source repository URL and its maintenance signals where the listing has one (bucketed star count, last commit and last release month, whether GitHub reports the repository archived, and the date ...
This record as markdown: /tools/directory-devrel-devrel-directory/get-listing.md
What get_listing does on DevRel Directory
AI agents call get_listing 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
slug | string | Yes | The listing slug, as returned by search_directory (e.g. 'answer-overflow'). |
Parameters from the server's own tool schema.
Why get_listing is rated Low
Even though get_listing 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.
Attacks that exploit this kind of access
The rule that runs get_listing 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 get_listing, this is the rule to start with:
get_listing 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 get_listing call is checked against it from then on.
Questions about get_listing
Get the full detail for one directory listing by its slug, including longer details when present, the source repository URL and its maintenance signals where the listing has one (bucketed star count, last commit and last release month, whether GitHub reports the repository archived, and the date all of those were checked), the slugs of similar listings, curated alternatives and complements (hand-picked substitutes and stack pairings, as slug + name), and any open DevRel jobs or upcoming events cross-linked to the same company. Returns an error for an unknown slug. It is categorised as a Read tool in the DevRel Directory MCP Server, which means it retrieves data without modifying state.
get_listing accepts 1 parameter: slug. Required: slug. The full parameter table on this page comes from the server's own tool schema.
Register the DevRel Directory MCP server in PolicyLayer and add a rule for get_listing: 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.
get_listing 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 get_listing 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 get_listing. 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.
get_listing 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