Get all object types and their metadata
AI agents call get_metadata_objects 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 descriptive information about available object types and their metadata structure. It has no side effects, does not execute code, does not modify data, and does not delete anything. It is a straightforward read operation that returns system schema/configuration information, comparable to a database DESCRIBE or schema inspection query.
From the tool's definition Tool name 'get_metadata_objects' and description 'Get all object types and their metadata' indicate a retrieval operation that queries system metadata without modifying or executing anything.
Documented attack patterns abuse exactly the kind of access get_metadata_objects 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_metadata_objects:
{
"version": "1",
"default": "deny",
"tools": {
"get_metadata_objects": {}
}
}get_metadata_objects 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 all object types and their metadata. 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_metadata_objects: 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_metadata_objects 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_metadata_objects 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_metadata_objects. 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_metadata_objects 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.