generate_trigger · Salesforce CLI MCP Server MCP

WHAT IT DOES

What generate_trigger does on Salesforce CLI MCP Server

AI agents use generate_trigger to create or update resources in Salesforce CLI MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Salesforce CLI MCP Server environment.

WHY IT NEEDS A POLICY

Why generate_trigger needs a policy

The tool creates new files (Apex trigger and metadata) in a Salesforce DX project, which constitutes data creation and modification. While the files themselves are reversible (can be deleted), the generation modifies the project state and could introduce code into the Salesforce org that affects business logic.

From the tool's definition Generates the Apex trigger *.trigger file and associated metadata file in a project; these are file creation operations that modify the project structure and Salesforce org configuration.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

generate_trigger Rate-limited

generate_trigger 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": {
    "generate_trigger": {
      "limits": [
        {
          "counter": "generate_trigger_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Salesforce CLI MCP Server, so you can run agents against it safely.

FAQ

Questions about generate_trigger

What does the generate_trigger tool do? +

Generates the Apex trigger *.trigger file and associated metadata file in a project. These files must be contained in a parent directory called. It is categorised as a Write tool in the Salesforce CLI MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on generate_trigger? +

Register the Salesforce CLI MCP Server MCP server in PolicyLayer and add a rule for generate_trigger: 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 CLI MCP Server. Nothing to install.

What risk level is generate_trigger? +

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

Can I rate-limit generate_trigger? +

Yes. Add a rate_limit block to the generate_trigger 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 generate_trigger completely? +

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

generate_trigger is provided by the Salesforce CLI MCP Server MCP server (perrynet/salesforce-cli-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.