depth can be provided to request your connectedAccount
AI agents call findOneConnectedAccount to retrieve information from Twenty 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 or fetches a single connected account entity. It performs a read-only query operation with no destructive, financial, or code execution implications. The depth parameter appears to control recursion/nesting in the response, which remains a read operation. Severity is low because the blast radius of misuse is limited to information disclosure of account connection metadata.
From the tool's definition Tool name 'findOneConnectedAccount' and description indicate retrieval of a single connected account record. The verb 'find' and 'request' denote query operations with no modification or side effects.
Documented attack patterns abuse exactly the kind of access findOneConnectedAccount gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Twenty MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for findOneConnectedAccount:
{
"version": "1",
"default": "deny",
"tools": {
"findOneConnectedAccount": {}
}
}findOneConnectedAccount 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.
depth can be provided to request your connectedAccount. 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 findOneConnectedAccount: 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.
findOneConnectedAccount 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 findOneConnectedAccount 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 findOneConnectedAccount. 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.
findOneConnectedAccount 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.
Start from Twenty 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.
219 Twenty MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.