Get metadata for a specific object type
AI agents call get_object_metadata 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 metadata about object types (schemas, field definitions, etc.) rather than modifying or deleting any data. It is purely informational and poses minimal risk if called by an AI agent, as metadata queries cannot alter business data or trigger external actions. The severity is low because the blast radius of misuse is limited to information disclosure of already-public schema information.
From the tool's definition Tool name contains 'get' and description states 'Get metadata for a specific object type' — a retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access get_object_metadata 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_object_metadata:
{
"version": "1",
"default": "deny",
"tools": {
"get_object_metadata": {}
}
} get_object_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 metadata for a specific object type. 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_object_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 CRM MCP Server. Nothing to install.
get_object_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_object_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_object_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_object_metadata 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.