Get a summary of all relationships for a specific entity (company or person)
AI agents call get_relationship_summary 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 queries and returns relationship data for a CRM entity. It performs no write, delete, execute, or financial operations—purely informational retrieval. The blast radius is minimal: at worst, an agent could access relationship information it shouldn't, but no data is modified, deleted, or executed.
From the tool's definition Tool name 'get_relationship_summary' and description 'Get a summary of all relationships for a specific entity' indicate a retrieval operation with no modification or side effects.
Documented attack patterns abuse exactly the kind of access get_relationship_summary 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 get_relationship_summary:
{
"version": "1",
"default": "deny",
"tools": {
"get_relationship_summary": {}
}
} get_relationship_summary 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 a summary of all relationships for a specific entity (company or 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 get_relationship_summary: 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.
get_relationship_summary 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_relationship_summary 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_relationship_summary. 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_relationship_summary is provided by the Twenty MCP Server MCP server (jezweb/twenty-mcp). 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.
29 Twenty MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.