AI agents call seq_starter_events_search 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 and queries log events from a Seq logging instance with bounded results and optional filtering. It has no side effects—it does not create, modify, delete, or execute operations. The 'bounded count' parameter and read-only nature of log search further confirm it is a safe Read operation. Severity is low because log data retrieval poses minimal risk even if misused by an AI agent.
From the tool's definition Tool name 'seq_starter_events_search' performs search operations with parameters like filter, signal id/name, and time window.
Attacks that exploit this kind of access
Search Seq events with a bounded count, optional Seq filter, signal id/name, UTC time window, and rendered message output. 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_events_search: 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_events_search 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_events_search 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_events_search. 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_events_search 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 →