approve_proposal
Approve a pending proposal and launch its draft campaign. SYNCHRONOUS — max-agent builds the prospect list, creates the campaign, and launches it (may take a while). Optionally pass modifications (titles, target_prospect_ids, campaign_name, campaign_description) to override the recommendation bef...
This record as markdown: /tools/digital-crew-technologies-max-mcp-server/approve-proposal.md
What approve_proposal does on Max MCP Server
AI agents invoke approve_proposal to trigger actions in Max MCP Server. 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.
Why approve_proposal is rated High
This tool triggers a multi-step external operation: building a prospect list, creating a campaign, and launching it. While it involves writes, the dominant action is triggering an automated campaign launch — an external operation with significant blast radius (messages sent to prospects). This maps to Execute.
From the tool's definition Approve a pending proposal and launch its draft campaign... max-agent builds the prospect list, creates the campaign, and launches it
Attacks that exploit this kind of access
The rule that runs approve_proposal 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 approve_proposal, this is the rule to start with:
approve_proposal stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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 approve_proposal call is checked against it from then on.
Questions about approve_proposal
Approve a pending proposal and launch its draft campaign. SYNCHRONOUS — max-agent builds the prospect list, creates the campaign, and launches it (may take a while). Optionally pass modifications (titles, target_prospect_ids, campaign_name, campaign_description) to override the recommendation before launch; omit them to approve as-is. On success returns {data: SignalProposal (status. It is categorised as a Execute tool in the Max MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Max MCP Server MCP server in PolicyLayer and add a rule for approve_proposal: 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.
approve_proposal 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 approve_proposal 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 approve_proposal. 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.
approve_proposal 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.
Across the catalogue