get_custom_field_values
Get custom field values for a CRM entity such as an account, contact, deal, or booking.
This record as markdown: /tools/io-favcrm-favcrm/get-custom-field-values.md
What get_custom_field_values does on FavCRM
AI agents call get_custom_field_values to retrieve information from FavCRM without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
entityId | string | Yes | Entity ID |
entityType | string | Yes | Entity type |
Parameters from the server's own tool schema.
Why get_custom_field_values is rated Low
This tool performs a read-only query of existing custom field data from CRM entities (account, contact, deal, booking). There is no data creation, modification, deletion, code execution, or financial impact. The worst case misuse is unauthorized information disclosure, which is relatively contained within the CRM domain and does not affect system integrity or external operations.
From the tool's definition Tool name is 'get_custom_field_values' and description states it 'Get custom field values' — a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs get_custom_field_values safely
PolicyLayer is an MCP gateway: it sits between your AI agents and FavCRM, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_custom_field_values, this is the rule to start with:
get_custom_field_values is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect FavCRM, apply this rule, and every get_custom_field_values call is checked against it from then on.
Questions about get_custom_field_values
Get custom field values for a CRM entity such as an account, contact, deal, or booking. It is categorised as a Read tool in the FavCRM MCP Server, which means it retrieves data without modifying state.
get_custom_field_values accepts 2 parameters: entityId, entityType. Required: entityId, entityType. The full parameter table on this page comes from the server's own tool schema.
Register the FavCRM MCP server in PolicyLayer and add a rule for get_custom_field_values: 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 FavCRM. Nothing to install.
get_custom_field_values is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_custom_field_values 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 get_custom_field_values. 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.
get_custom_field_values is provided by the FavCRM MCP server (https://api.favcrm.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FavCRM, and thousands of servers like it.
This server
Across the catalogue