subscribe
Create a proactive monitoring subscription to a live-data event stream. Returns the new subscription id. Requires a Pipeworx OAuth account (anonymous + BYO cannot persist subscriptions). Supported types: "sec_8k" (8-K filings matching ticker + item codes — e.g. items:["5.02"] = officer change), "...
This record as markdown: /tools/io-github-pipeworx-io-linear/subscribe.md
What subscribe does on Linear
AI agents use subscribe to create or update resources in Linear, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Linear environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
type | string | Yes | Subscription type. |
params | object | Yes | Type-specific filter. sec_8k: {ticker:"AAPL", items?:["5.02","1.01"]}. polymarket_edge: {topic:"fed", min_spread_bps?:500}. fred_series: {series_id:"UNRATE"}. p |
delivery | object | — | Optional delivery channels in addition to the always-on persistent feed. {email:"you@x.com"} sends a templated alert per fired event. {sms:"+15551234567"} sends |
Parameters from the server's own tool schema.
Why subscribe is rated Medium
This tool creates and modifies subscription records—a reversible write operation. It does not execute queries, delete data, or move money. The severity is medium because misuse could create unwanted subscriptions consuming resources or enabling information exfiltration via email delivery of sensitive market data (8-K filings, mispricings), but subscriptions can be deleted/modified later.
From the tool's definition Tool creates a 'proactive monitoring subscription' that returns a 'new subscription id', persisting state in a user's account.
Risk signalsAccepts URL/endpoint input (delivery.webhook)
Attacks that exploit this kind of access
The rule that runs subscribe safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Linear, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For subscribe, this is the rule to start with:
subscribe stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Linear, apply this rule, and every subscribe call is checked against it from then on.
Questions about subscribe
Create a proactive monitoring subscription to a live-data event stream. Returns the new subscription id. Requires a Pipeworx OAuth account (anonymous + BYO cannot persist subscriptions). Supported types: "sec_8k" (8-K filings matching ticker + item codes — e.g. items:["5.02"] = officer change), "polymarket_edge" (Polymarket↔Kalshi cross-venue mispricings — params:{topic:"fed"}), "fred_series" (new FRED observations — params:{series_id:"UNRATE"}). Delivery channels: feed (always on — pull via recent_alerts or GET registry.pipeworx.io/alerts.json), and optionally email (set delivery:{email:"you@x.com"}) or sms (delivery:{sms:"+15551234567"} — phone must be verified at /account first; 10/day cap). It is categorised as a Write tool in the Linear MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
subscribe accepts 3 parameters: type, params, delivery. Required: type, params. The full parameter table on this page comes from the server's own tool schema.
Register the Linear MCP server in PolicyLayer and add a rule for subscribe: 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 Linear. Nothing to install.
subscribe is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the subscribe 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 subscribe. 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.
subscribe is provided by the Linear MCP server (https://gateway.pipeworx.io/linear/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Linear, and thousands of servers like it.
This server
Across the catalogue