attach_campaign_to_intent_trigger
Link an existing campaign to up to 20 intent triggers so a changed signal auto-launches it. Idempotent. Returns {data: {attached, requested}}; 404 if the campaign or none of the triggers are in this workspace.
This record as markdown: /tools/digital-crew-technologies-max-mcp-server/attach-campaign-to-intent-trigger.md
What attach_campaign_to_intent_trigger does on Max MCP Server
AI agents use attach_campaign_to_intent_trigger to create or update resources in Max MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Max MCP Server environment.
Why attach_campaign_to_intent_trigger is rated Medium
Modifies campaign-trigger associations, automatically launching campaigns when signals change; high blast radius if triggered incorrectly.
From the tool's definition Link an existing campaign to intent triggers; auto-launches.
Attacks that exploit this kind of access
The rule that runs attach_campaign_to_intent_trigger safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Max MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For attach_campaign_to_intent_trigger, this is the rule to start with:
attach_campaign_to_intent_trigger 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 Max MCP Server, apply this rule, and every attach_campaign_to_intent_trigger call is checked against it from then on.
Questions about attach_campaign_to_intent_trigger
Link an existing campaign to up to 20 intent triggers so a changed signal auto-launches it. Idempotent. Returns {data: {attached, requested}}; 404 if the campaign or none of the triggers are in this workspace. It is categorised as a Write tool in the Max MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Max MCP Server MCP server in PolicyLayer and add a rule for attach_campaign_to_intent_trigger: 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 Max MCP Server. Nothing to install.
attach_campaign_to_intent_trigger 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 attach_campaign_to_intent_trigger 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 attach_campaign_to_intent_trigger. 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.
attach_campaign_to_intent_trigger is provided by the Max MCP Server MCP server (digital-crew-technologies/max-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Max MCP Server, and thousands of servers like it.
This server
Across the catalogue