AI agents invoke seq_api_request to trigger actions in Seq. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool allows execution of API requests to Seq instances. While the server description emphasizes 'controlled read access,' this specific tool (seq_api_request) lacks explicit guardrails limiting it to read-only operations.
From the tool's definition Execute an advanced Seq API request against an official cataloged route template—tool directly executes arbitrary API requests against live Seq instances, with potential to invoke any cataloged route.
Attacks that exploit this kind of access
Execute an advanced Seq API request against an official cataloged route template. Use seq_api_catalog first to choose method/path. It is categorised as a Execute tool in the Seq MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Seq MCP server in PolicyLayer and add a rule for seq_api_request: 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_api_request is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the seq_api_request 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_api_request. 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_api_request 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 →