contact_update
Update an existing contact/company in AbraFlexi.
This record as markdown: /tools/abraflexi/contact-update.md
What contact_update does on AbraFlexi
AI agents use contact_update to create or update resources in AbraFlexi, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AbraFlexi environment.
Why contact_update is rated Medium
The tool modifies data reversibly by updating contact/company records. While it affects important business data (contacts), it does not delete data (would be Destructive), move money (Financial), or execute arbitrary code (Execute). The 'medium' severity reflects that contact data corruption could disrupt business operations, but the reversible nature prevents a 'high' rating.
From the tool's definition Tool name 'contact_update' and description 'Update an existing contact/company in AbraFlexi' explicitly indicate modification of existing data.
Attacks that exploit this kind of access
The rule that runs contact_update safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AbraFlexi, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For contact_update, this is the rule to start with:
contact_update 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 AbraFlexi, apply this rule, and every contact_update call is checked against it from then on.
Questions about contact_update
Update an existing contact/company in AbraFlexi. It is categorised as a Write tool in the AbraFlexi MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the AbraFlexi MCP server in PolicyLayer and add a rule for contact_update: 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 AbraFlexi. Nothing to install.
contact_update 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 contact_update 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 contact_update. 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.
contact_update is provided by the AbraFlexi MCP server (abraflexi-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on AbraFlexi, and thousands of servers like it.
This server
Across the catalogue