findOnePerson
depth can be provided to request your person
This record as markdown: /tools/jdu278-twenty-mcp-server/findoneperson.md
What findOnePerson does on Twenty MCP Server
AI agents call findOnePerson to retrieve information from Twenty MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why findOnePerson is rated Low
This tool queries and retrieves CRM person data without modifying, deleting, or executing operations. The 'find' operation is a standard read/retrieval operation. The depth parameter allows control over related record inclusion but does not alter data. No side effects or destructive capabilities are evident.
From the tool's definition Tool name 'findOnePerson' and description indicating it retrieves a single person record with optional depth parameter for related data.
Attacks that exploit this kind of access
The rule that runs findOnePerson safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Twenty MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For findOnePerson, this is the rule to start with:
findOnePerson 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 Twenty MCP Server, apply this rule, and every findOnePerson call is checked against it from then on.
Questions about findOnePerson
depth can be provided to request your person. It is categorised as a Read tool in the Twenty MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Twenty MCP Server MCP server in PolicyLayer and add a rule for findOnePerson: 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 MCP Server. Nothing to install.
findOnePerson 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 findOnePerson 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 findOnePerson. 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.
findOnePerson is provided by the Twenty MCP Server MCP server (jdu278/twenty-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Twenty MCP Server, and thousands of servers like it.
This server
Across the catalogue