AI agents call seq_starter_event_by_id to retrieve information from Seq without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves a single event record from a Seq logging instance by its identifier. Fetching log data has no destructive, modifying, or executable side effects. The optional rendering of message text is still read-only. This is a straightforward Read operation with low blast radius if misused by an agent.
From the tool's definition Tool description states 'Fetch one Seq event by event id' — a retrieval operation with no side effects. The server description emphasizes 'controlled read access' and 'search events, execute data queries, and retrieve information'.
Attacks that exploit this kind of access
Fetch one Seq event by event id, optionally including rendered message text. It is categorised as a Read tool in the Seq MCP Server, which means it retrieves data without modifying state.
Register the Seq MCP server in PolicyLayer and add a rule for seq_starter_event_by_id: 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 Seq. Nothing to install.
seq_starter_event_by_id 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 seq_starter_event_by_id 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 seq_starter_event_by_id. 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.
seq_starter_event_by_id is provided by the Seq MCP server (mclifeleader/seq-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →