This record as markdown: /tools/io-favcrm-favcrm/get-contact.md
What get_contact does on FavCRM
AI agents call get_contact 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 |
|---|---|---|---|
contactId | string | Yes | The contact ID |
Parameters from the server's own tool schema.
Why get_contact is rated Low
This tool performs a read-only query to retrieve contact data. It does not create, modify, delete, or execute any operations—it simply fetches an existing record by identifier. The blast radius of misuse is minimal, limited to potential exposure of contact information already in the system. This is classified as a Read operation with low severity.
From the tool's definition The tool is named 'get_contact' and described as 'Fetch a single contact by ID', which is a straightforward retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs get_contact 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_contact, this is the rule to start with:
get_contact 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_contact call is checked against it from then on.
Questions about get_contact
Fetch a single contact by ID. It is categorised as a Read tool in the FavCRM MCP Server, which means it retrieves data without modifying state.
get_contact accepts 1 parameter: contactId. Required: contactId. 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_contact: 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_contact 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_contact 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_contact. 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_contact 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