This record as markdown: /tools/abraflexi/contact-create.md
What contact_create does on AbraFlexi
AI agents use contact_create 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_create is rated Medium
The contact_create tool creates new contact records, which is a reversible write operation. While the description is empty (lowering confidence slightly), the naming pattern and context of sibling contact management tools strongly suggest contact data creation.
From the tool's definition Tool name 'contact_create' combined with sibling tools (contact_delete, contact_update, contact_get) indicates CRUD operations on contact records. The pattern is consistent with data creation.
Attacks that exploit this kind of access
The rule that runs contact_create 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_create, this is the rule to start with:
contact_create 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_create call is checked against it from then on.
Questions about contact_create
contact_create is a write tool on the AbraFlexi MCP server. 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_create: 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_create 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_create 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_create. 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_create 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