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), "...
AI agents use subscribe to create or update resources in Mcp Theaudiodb — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Theaudiodb 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.
This tool creates and modifies data (a subscription record) with reversible side effects—subscriptions can be managed, updated, or deleted by the user. It is not a simple read (it persists new state), not Execute (no code/script execution or arbitrary external trigger), not Destructive (subscriptions are not irreversible), and not Financial (no money movement).
From the tool's definition Tool creates a persistent subscription to data event streams ('Create a proactive monitoring subscription', 'Returns the new subscription id'), persisting state in a backend system that requires OAuth authentication.
Risk signalsAccepts URL/endpoint input (delivery.webhook)
Attacks that exploit this kind of access
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 Mcp Theaudiodb 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 Mcp Theaudiodb 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 Mcp Theaudiodb. 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 Mcp Theaudiodb MCP server (https://gateway.pipeworx.io/theaudiodb/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 →