List Apex triggers in the organization with optional name filtering
AI agents call list_apex_triggers to retrieve information from Salesforce without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs a read-only operation that retrieves and filters existing Apex triggers without creating, modifying, deleting, or executing any code. It is a metadata introspection capability consistent with other read tools on this server like 'describe_sobject' and 'describe_tooling_object'. The optional filtering parameter does not change the read-only nature of the operation.
From the tool's definition Tool name 'list_apex_triggers' and description 'List Apex triggers in the organization with optional name filtering' indicate a query/retrieval operation with no modification or deletion of data.
Documented attack patterns abuse exactly the kind of access list_apex_triggers gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Salesforce, and nothing reaches the server without passing your rules. This is the rule we recommend for list_apex_triggers:
{
"version": "1",
"default": "deny",
"tools": {
"list_apex_triggers": {}
}
}list_apex_triggers 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.
List Apex triggers in the organization with optional name filtering. It is categorised as a Read tool in the Salesforce MCP Server, which means it retrieves data without modifying state.
Register the Salesforce MCP server in PolicyLayer and add a rule for list_apex_triggers: 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. Nothing to install.
list_apex_triggers 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 list_apex_triggers 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 list_apex_triggers. 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.
list_apex_triggers is provided by the Salesforce MCP server (ryu-727/salesforce-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Salesforce, 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.
25 Salesforce tools catalogued and risk-classified — across an index of 43,000+ MCP servers.