relays_ingestErrorEvent
Ingest one Sentry-shaped application error event (POST /v1/relays/errors/events)
This record as markdown: /tools/onesi-genesis-mcp/relays-ingesterrorevent.md
What relays_ingestErrorEvent does on Genesis
AI agents call relays_ingestErrorEvent to retrieve information from Genesis 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 |
|---|---|---|---|
body | object | Yes | Sentry-shaped event; every field is optional and read leniently. |
Parameters from the server's own tool schema.
Why relays_ingestErrorEvent is rated Low
Even though relays_ingestErrorEvent 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 signalsAccepts raw HTML/template content (body) · High parameter count (20 properties)
Attacks that exploit this kind of access
The rule that runs relays_ingestErrorEvent safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Genesis, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For relays_ingestErrorEvent, this is the rule to start with:
relays_ingestErrorEvent 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 Genesis, apply this rule, and every relays_ingestErrorEvent call is checked against it from then on.
Questions about relays_ingestErrorEvent
Ingest one Sentry-shaped application error event (POST /v1/relays/errors/events). It is categorised as a Read tool in the Genesis MCP Server, which means it retrieves data without modifying state.
relays_ingestErrorEvent accepts 1 parameter: body. Required: body. The full parameter table on this page comes from the server's own tool schema.
Register the Genesis MCP server in PolicyLayer and add a rule for relays_ingestErrorEvent: 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 Genesis. Nothing to install.
relays_ingestErrorEvent 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 relays_ingestErrorEvent 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 relays_ingestErrorEvent. 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.
relays_ingestErrorEvent is provided by the Genesis MCP server (@onesi/genesis-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Genesis, and thousands of servers like it.
This server
Across the catalogue