add_agreement_addition
AI agents use add_agreement_addition to create or update resources in ConnectWise Live MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ConnectWise Live MCP Server environment.
The tool adds an addition to an agreement, which is a write operation that creates or modifies agreement records. No description is provided, lowering confidence slightly, but the naming convention and sibling context strongly indicate a Write category.
From the tool's definition Tool name 'add_agreement_addition' indicates creation/modification of agreement data. Sibling tools include 'create_agreement', 'create_opportunity', 'create_project', and 'create_ticket', which are clearly Write operations.
Attacks that exploit this kind of access
add_agreement_addition. It is categorised as a Write tool in the ConnectWise Live MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ConnectWise Live MCP Server MCP server in PolicyLayer and add a rule for add_agreement_addition: 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 ConnectWise Live MCP Server. Nothing to install.
add_agreement_addition 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 add_agreement_addition 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 add_agreement_addition. 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.
add_agreement_addition is provided by the ConnectWise Live MCP Server MCP server (mfrostbutter/connectwise-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →