Get Apex Triggers by SObject
AI agents call triggers-by-sobject to retrieve information from Salesforce MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about Apex triggers without executing them, modifying data, or causing side effects. It is a read-only operation that queries Salesforce configuration information. While it provides visibility into automation rules (which could inform a subsequent attack), the tool itself performs no destructive, executable, or financial actions.
From the tool's definition The tool name 'triggers-by-sobject' and description 'Get Apex Triggers by SObject' indicate a retrieval operation that queries/fetches trigger metadata associated with Salesforce objects.
Attacks that exploit this kind of access
Get Apex Triggers by SObject. It is categorised as a Read tool in the Salesforce MCP MCP Server, which means it retrieves data without modifying state.
Register the Salesforce MCP server in PolicyLayer and add a rule for triggers-by-sobject: 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 MCP. Nothing to install.
triggers-by-sobject 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 triggers-by-sobject 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 triggers-by-sobject. 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.
triggers-by-sobject is provided by the Salesforce MCP server (jpmonette/salesforce-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →