sf_create_custom_metadata_type
Creates a new Custom Metadata Type (ending in __mdt) with optional custom fields. Custom Metadata Types store configuration data that can be packaged and deployed. Use when a user wants to store configuration in metadata rather than custom objects.
This record as markdown: /tools/io-github-semwalajay83-sem-salesforce-metadata-mcp/sf-create-custom-metadata-type.md
What sf_create_custom_metadata_type does on Salesforce Metadata Mcp
AI agents use sf_create_custom_metadata_type to create or update resources in Salesforce Metadata Mcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Salesforce Metadata Mcp environment.
Why sf_create_custom_metadata_type is rated Medium
The tool creates new metadata structures (reversible via deletion/deactivation) rather than executing arbitrary code or deleting data. It modifies org configuration but does not execute commands, trigger financial transactions, or irreversibly destroy data. Classification as Write is appropriate because metadata creation can be undone through standard Salesforce metadata deployment/deletion processes.
From the tool's definition Tool description states it 'Creates a new Custom Metadata Type' — this is a create operation that modifies the Salesforce org's metadata structure by adding new configuration storage types with 'optional custom fields'.
Attacks that exploit this kind of access
The rule that runs sf_create_custom_metadata_type safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Salesforce Metadata Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For sf_create_custom_metadata_type, this is the rule to start with:
sf_create_custom_metadata_type stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Salesforce Metadata Mcp, apply this rule, and every sf_create_custom_metadata_type call is checked against it from then on.
Questions about sf_create_custom_metadata_type
Creates a new Custom Metadata Type (ending in __mdt) with optional custom fields. Custom Metadata Types store configuration data that can be packaged and deployed. Use when a user wants to store configuration in metadata rather than custom objects. It is categorised as a Write tool in the Salesforce Metadata Mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Salesforce Metadata MCP server in PolicyLayer and add a rule for sf_create_custom_metadata_type: 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 Salesforce Metadata Mcp. Nothing to install.
sf_create_custom_metadata_type is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the sf_create_custom_metadata_type 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 sf_create_custom_metadata_type. 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.
sf_create_custom_metadata_type is provided by the Salesforce Metadata MCP server (salesforce-metadata-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Salesforce Metadata, and thousands of servers like it.
This server
Across the catalogue