update_agreement · ConnectWise Live MCP Server MCP

WHAT IT DOES

What update_agreement does on ConnectWise Live MCP Server

AI agents use update_agreement 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.

WHY IT NEEDS A POLICY

Why update_agreement needs a policy

The 'update' verb and 'agreement' object classify this as a Write operation—it creates or modifies data reversibly. Agreements are core business records in ConnectWise, so unauthorized modification could disrupt service delivery or contract terms, warranting medium severity. Confidence is moderately high based on the naming convention, though the empty description limits certainty.

From the tool's definition Tool name 'update_agreement' indicates modification of agreement data. No description provided, but the name strongly suggests reversible data modification in a business context (ConnectWise Manage).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_agreement Rate-limited

update_agreement 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_agreement": {
      "limits": [
        {
          "counter": "update_agreement_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches ConnectWise Live MCP Server, so you can run agents against it safely.

FAQ

Questions about update_agreement

What does the update_agreement tool do? +

update_agreement. 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.

How do I enforce a policy on update_agreement? +

Register the ConnectWise Live MCP Server MCP server in PolicyLayer and add a rule for update_agreement: 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.

What risk level is update_agreement? +

update_agreement is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_agreement? +

Yes. Add a rate_limit block to the update_agreement 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.

How do I block update_agreement completely? +

Set action: deny in the PolicyLayer policy for update_agreement. 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.

What MCP server provides update_agreement? +

update_agreement 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.