get_event_graph

Get event/signal/task dispatch graph (Laravel events, Django signals, NestJS events, Celery tasks, Socket.io events). Use to understand event-driven architecture and trace event producers/consumers. Read-only. Returns JSON: { events: [{ name, dispatchers, listeners, file }] }.

SERVERTrace SOURCEnikolai-vysotskyi/trace-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/nikolai-vysotskyi-trace-mcp/get-event-graph.md

WHAT IT DOES

What get_event_graph does on Trace

AI agents call get_event_graph to retrieve information from Trace without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_event_graph is rated Low

get_event_graph retrieves and queries dependency graph information about events and tasks across multiple frameworks. It performs analysis and navigation of existing code structure without creating, modifying, deleting, or executing any code. This is a classic read operation with no destructive, financial, or execution capabilities.

From the tool's definition Tool description explicitly states "Read-only" and returns JSON data about event graphs. The operation is to "understand event-driven architecture and trace event producers/consumers" with no modifications or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_event_graph safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Trace, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_event_graph, this is the rule to start with:

get_event_graph Allowed

get_event_graph is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_event_graph": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Trace, apply this rule, and every get_event_graph call is checked against it from then on.

FAQ

Questions about get_event_graph

What does the get_event_graph tool do? +

How do I enforce a policy on get_event_graph? +

Register the Trace MCP server in PolicyLayer and add a rule for get_event_graph: 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 Trace. Nothing to install.

What risk level is get_event_graph? +

get_event_graph is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_event_graph? +

Yes. Add a rate_limit block to the get_event_graph 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.

How do I block get_event_graph completely? +

Set action: deny in the PolicyLayer policy for get_event_graph. 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.

What MCP server provides get_event_graph? +

get_event_graph is provided by the Trace MCP server (nikolai-vysotskyi/trace-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Trace, and thousands of servers like it.

This server

All 191 Trace tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server →get_customer_data on 08-AI-Business-Agent → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →