update_campaign_memory
Record/update Max
This record as markdown: /tools/digital-crew-technologies-max-mcp-server/update-campaign-memory.md
What update_campaign_memory does on Max MCP Server
AI agents use update_campaign_memory 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 update_campaign_memory is rated Medium
The tool creates or modifies data reversibly within the workspace profile settings for the Digital Crew Max sales agent. 'Update' operations are Write-category by definition. Severity is medium because misconfiguration of campaign memory could impact sales workflows and data consistency, but changes are typically reversible.
From the tool's definition Tool name includes 'update' and description states 'Record/update Max', indicating modification of data (campaign memory/settings) rather than deletion or destruction.
Attacks that exploit this kind of access
The rule that runs update_campaign_memory 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 update_campaign_memory, this is the rule to start with:
update_campaign_memory 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 update_campaign_memory call is checked against it from then on.
Questions about update_campaign_memory
Record/update Max. 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 update_campaign_memory: 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.
update_campaign_memory 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 update_campaign_memory 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 update_campaign_memory. 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.
update_campaign_memory 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