AI agents call get_person to retrieve information from Twenty CRM MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about a single person record from the CRM database. It performs a query operation that only reads data without creating, modifying, deleting, or executing any external actions. The minimal blast radius if misused is exposure of customer personal data stored in the CRM, which is a confidentiality concern but not an immediate operational risk. Classified as Read with low severity.
From the tool's definition Tool name is 'get_person' and description states 'Get details of a specific person by ID' — a retrieval operation with no modification or side effects.
Documented attack patterns abuse exactly the kind of access get_person gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Twenty CRM MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_person:
{
"version": "1",
"default": "deny",
"tools": {
"get_person": {}
}
}get_person is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
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.
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.
get_person 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_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.
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.
get_person is provided by the Twenty CRM MCP Server MCP server (mhenry3164/twenty-crm-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Twenty 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.
23 Twenty CRM MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.