List, get, create, update, or delete contact fields like email addresses, phone numbers, social media handles, etc. Use this simplified tool instead of monica_manage_contact when managing contact fields. Provide contactId and fieldPayload with data and contactFieldTypeName (e.g.,
AI agents use monica_manage_contact_field to create or update resources in Monica CRM MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Monica CRM MCP Server environment.
This tool primarily enables Write operations (create, update) on contact field data within Monica CRM. While delete is mentioned, the core functionality emphasized is reversible modification of contact attributes. The delete aspect prevents a higher Write classification, but deletion of individual contact fields (not entire contacts) is less severe than full contact deletion.
From the tool's definition Tool performs create, update, or delete operations on contact fields (email addresses, phone numbers, social media handles). Description explicitly states 'create, update, or delete contact fields'.
Documented attack patterns abuse exactly the kind of access monica_manage_contact_field gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Monica CRM MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for monica_manage_contact_field:
{
"version": "1",
"default": "deny",
"tools": {
"monica_manage_contact_field": {
"limits": [
{
"counter": "monica_manage_contact_field_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}monica_manage_contact_field 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.
Free to start. No card required.
List, get, create, update, or delete contact fields like email addresses, phone numbers, social media handles, etc. Use this simplified tool instead of monica_manage_contact when managing contact fields. Provide contactId and fieldPayload with data and contactFieldTypeName (e.g.,. It is categorised as a Write tool in the Monica CRM MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Monica CRM MCP Server MCP server in PolicyLayer and add a rule for monica_manage_contact_field: 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 Monica CRM MCP Server. Nothing to install.
monica_manage_contact_field 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 monica_manage_contact_field 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 monica_manage_contact_field. 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.
monica_manage_contact_field is provided by the Monica CRM MCP Server MCP server (jacob-stokes/monica-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Monica CRM MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
21 Monica CRM MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.