get_custom_field_values

Get custom field values for a CRM entity such as an account, contact, deal, or booking.

SERVERFavCRM SOURCEhttps://api.favcrm.io/mcp
Low RISK CLASS
Category Read
Parameters 22 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

ParameterTypeRequiredDescription
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.

Questions about get_custom_field_values

What does the get_custom_field_values tool do? +

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.

What parameters does get_custom_field_values accept? +

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.

How do I enforce a policy on get_custom_field_values? +

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.

What risk level is get_custom_field_values? +

get_custom_field_values is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_custom_field_values? +

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.

How do I block get_custom_field_values completely? +

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.

What MCP server provides get_custom_field_values? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of FavCRM's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.