list_events
List DevRel events and conferences with their call-for-papers deadlines. Defaults to upcoming events only; set upcomingOnly to false to include past events, or cfpOpenOnly to true to keep only events whose CFP is still open. Each result includes the external event url and a canonicalUrl to the ev...
This record as markdown: /tools/directory-devrel-devrel-directory/list-events.md
What list_events does on DevRel Directory
AI agents call list_events 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 |
|---|---|---|---|
cfpOpenOnly | boolean | — | When true, only events whose call for papers is still accepting submissions. |
upcomingOnly | boolean | — | Default true; set false to include events that have already started or ended. |
Parameters from the server's own tool schema.
Why list_events is rated Low
Even though list_events 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 list_events 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 list_events, this is the rule to start with:
list_events 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 list_events call is checked against it from then on.
Questions about list_events
List DevRel events and conferences with their call-for-papers deadlines. Defaults to upcoming events only; set upcomingOnly to false to include past events, or cfpOpenOnly to true to keep only events whose CFP is still open. Each result includes the external event url and a canonicalUrl to the events page on devrel.directory. It is categorised as a Read tool in the DevRel Directory MCP Server, which means it retrieves data without modifying state.
list_events accepts 2 parameters: cfpOpenOnly, upcomingOnly. 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 list_events: 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.
list_events 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 list_events 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 list_events. 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.
list_events 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