sf_create_custom_notification_type

SERVERSalesforce Metadata Mcp SOURCEsalesforce-metadata-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-semwalajay83-sem-salesforce-metadata-mcp/sf-create-custom-notification-type.md

WHAT IT DOES

What sf_create_custom_notification_type does on Salesforce Metadata Mcp

AI agents use sf_create_custom_notification_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.

RISK

Why sf_create_custom_notification_type is rated Medium

This tool creates a new metadata configuration (Custom Notification Type) that is reversible—it can be modified or deleted later. It does not execute arbitrary code, delete data, move money, or cause irreversible changes.

From the tool's definition Creates a Custom Notification Type that can be sent from Flows, Apex, or Process Builder. The verb 'Creates' and the phrase 'create in-app alerts' indicate a new configuration object is being added to the Salesforce environment.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs sf_create_custom_notification_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_notification_type, this is the rule to start with:

sf_create_custom_notification_type Rate-limited

sf_create_custom_notification_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "sf_create_custom_notification_type": {
      "limits": [
        {
          "counter": "sf_create_custom_notification_type_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Salesforce Metadata Mcp, apply this rule, and every sf_create_custom_notification_type call is checked against it from then on.

FAQ

Questions about sf_create_custom_notification_type

What does the sf_create_custom_notification_type tool do? +

Creates a Custom Notification Type that can be sent from Flows, Apex, or Process Builder using the Send Custom Notification action. Custom Notifications appear in Salesforce notification bell (and optionally mobile push). Use to create in-app alerts for important business events. 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.

How do I enforce a policy on sf_create_custom_notification_type? +

Register the Salesforce Metadata MCP server in PolicyLayer and add a rule for sf_create_custom_notification_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.

What risk level is sf_create_custom_notification_type? +

sf_create_custom_notification_type is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit sf_create_custom_notification_type? +

Yes. Add a rate_limit block to the sf_create_custom_notification_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.

How do I block sf_create_custom_notification_type completely? +

Set action: deny in the PolicyLayer policy for sf_create_custom_notification_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.

What MCP server provides sf_create_custom_notification_type? +

sf_create_custom_notification_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.

KEEP EXPLORING

More on Salesforce Metadata, and thousands of servers like it.

This server

All 213 Salesforce Metadata tools →

Across the catalogue

create_task on 0rca Dojo MCP Server →create-task on Kanban MCP Server →create_package_backup on Android Forensics ADB MCP Server →create_project on Stitch MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →