Update an existing party by ID.
AI agents use update_party_tool to create or update resources in Capsulecrm — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Capsulecrm environment.
The tool creates or modifies CRM data (party records) in a reversible manner. Updates are Write operations as they change existing records without permanently destroying them. Severity is medium because modifying customer/party data in a CRM can have significant business impact (incorrect contact info, relationships, or attributes) but is theoretically reversible through further updates or system recovery.
From the tool's definition Tool name contains 'update' and description states 'Update an existing party by ID.' This operation modifies existing data in the CRM system.
Attacks that exploit this kind of access
Update an existing party by ID. It is categorised as a Write tool in the Capsulecrm MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Capsulecrm MCP server in PolicyLayer and add a rule for update_party_tool: 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 Capsulecrm. Nothing to install.
update_party_tool 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_party_tool 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_party_tool. 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_party_tool is provided by the Capsulecrm MCP server (monadsag/capsulecrm-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 →