get_person

Get details of a specific person by ID

SERVERTwenty CRM MCP Server SOURCEdenisalmeida/twenty-crm-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/denisalmeida-twenty-crm-mcp/get-person.md

WHAT IT DOES

What get_person does on Twenty CRM MCP Server

AI agents call get_person to retrieve information from Twenty CRM MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_person is rated Low

This tool retrieves and queries existing person data from the CRM by identifier. It does not modify, delete, or execute any operations—it simply fetches information. This is a standard Read operation with minimal risk even if an AI agent misuses it, as the worst outcome is unauthorized information disclosure rather than data loss or execution of external commands.

From the tool's definition Tool name 'get_person' and description 'Get details of a specific person by ID' indicate a retrieval operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_person safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Twenty CRM MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_person, this is the rule to start with:

get_person Allowed

get_person is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_person": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Twenty CRM MCP Server, apply this rule, and every get_person call is checked against it from then on.

FAQ

Questions about get_person

What does the get_person tool do? +

Get details of a specific person by ID. It is categorised as a Read tool in the Twenty CRM MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_person? +

Register the Twenty CRM MCP Server MCP server in PolicyLayer and add a rule for get_person: 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 Twenty CRM MCP Server. Nothing to install.

What risk level is get_person? +

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

Can I rate-limit get_person? +

Yes. Add a rate_limit block to the get_person 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_person completely? +

Set action: deny in the PolicyLayer policy for get_person. 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_person? +

get_person is provided by the Twenty CRM MCP Server MCP server (denisalmeida/twenty-crm-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Twenty CRM MCP Server, and thousands of servers like it.

This server

All 35 Twenty CRM MCP Server tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →