Get detailed information about fields, either for a specific object or across all objects
AI agents call get_field_metadata 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 metadata about field definitions in the CRM system. It performs a read-only query operation that returns structural information about the data model without creating, modifying, deleting, or executing any actions. The blast radius of misuse is minimal since metadata disclosure alone does not compromise core data or trigger external operations.
From the tool's definition Tool name is 'get_field_metadata' and description states 'Get detailed information about fields' — a retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access get_field_metadata 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_field_metadata:
{
"version": "1",
"default": "deny",
"tools": {
"get_field_metadata": {}
}
} get_field_metadata 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 detailed information about fields, either for a specific object or across all objects. 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_field_metadata: 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_field_metadata 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_field_metadata 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_field_metadata. 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_field_metadata 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.