outbound_sequencer
Séquences outbound — Gapup agent-payable C-suite expertise (CRO). Returns a structured, audited deliverable. Reference case: Gapup Hub → CFO + CRO B2B SaaS France — Séquence 6 touches multi-canal · Taux réponse +180%. Inputs are validated server-side — send the documented case fields.
This record as markdown: /tools/io-github-getgapup-gapup-mcp/outbound-sequencer.md
What outbound_sequencer does on Gapup Mcp
AI agents use outbound_sequencer to create or update resources in Gapup Mcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gapup Mcp environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
icp | object | Yes | |
async | boolean | — | If true, returns a job_id immediately (<200ms) instead of waiting for the result. Poll the result with job_result(job_id). Use for slow tools to avoid client ti |
offer | object | Yes | |
excludedAngles | string | — | |
targetAccounts | array | — |
Parameters from the server's own tool schema.
Why outbound_sequencer is rated Medium
The tool creates and configures outbound communication sequences targeting business decision-makers (C-suite: CFO, CRO). While it does not delete or execute arbitrary code, it initiates irreversible business communications and engagement workflows.
From the tool's definition Tool name 'outbound_sequencer' combined with description stating it 'Séquences outbound' and references 'multi-canal' engagement with documented case fields and response rate metrics.
Risk signalsHigh parameter count (12 properties)
Attacks that exploit this kind of access
The rule that runs outbound_sequencer safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gapup Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For outbound_sequencer, this is the rule to start with:
outbound_sequencer 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 Gapup Mcp, apply this rule, and every outbound_sequencer call is checked against it from then on.
Questions about outbound_sequencer
Séquences outbound — Gapup agent-payable C-suite expertise (CRO). Returns a structured, audited deliverable. Reference case: Gapup Hub → CFO + CRO B2B SaaS France — Séquence 6 touches multi-canal · Taux réponse +180%. Inputs are validated server-side — send the documented case fields. It is categorised as a Write tool in the Gapup Mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
outbound_sequencer accepts 5 parameters: icp, async, offer, excludedAngles, targetAccounts. Required: icp, offer. The full parameter table on this page comes from the server's own tool schema.
Register the Gapup MCP server in PolicyLayer and add a rule for outbound_sequencer: 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 Gapup Mcp. Nothing to install.
outbound_sequencer 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 outbound_sequencer 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 outbound_sequencer. 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.
outbound_sequencer is provided by the Gapup MCP server (https://mcp.gapup.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gapup, and thousands of servers like it.
This server
Across the catalogue