update_sales_catalog_item
REPLACE a catalog item: omitted optional fields reset to defaults, so send the full record plus expected_updated_at (its current updated_at; 409 if it changed). Returns {data: Offering}.
This record as markdown: /tools/digital-crew-technologies-max-mcp-server/update-sales-catalog-item.md
What update_sales_catalog_item does on Max MCP Server
AI agents use update_sales_catalog_item 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_sales_catalog_item is rated Medium
Modifies existing sales catalog item data reversibly; includes safeguard via expected_updated_at concurrency check.
From the tool's definition REPLACE a catalog item; omitted optional fields reset to defaults
Attacks that exploit this kind of access
The rule that runs update_sales_catalog_item 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_sales_catalog_item, this is the rule to start with:
update_sales_catalog_item 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_sales_catalog_item call is checked against it from then on.
Questions about update_sales_catalog_item
REPLACE a catalog item: omitted optional fields reset to defaults, so send the full record plus expected_updated_at (its current updated_at; 409 if it changed). Returns {data: Offering}. 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_sales_catalog_item: 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_sales_catalog_item 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_sales_catalog_item 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_sales_catalog_item. 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_sales_catalog_item 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