Use case · Salesforce
FlagshipAI Agent Action Security for Salesforce
AI Agent Action Security for Salesforce is the assessment of a specific proposed agent action in Salesforce — an export, a bulk update, a deletion, an account change — before that action executes. Asyrx returns an Action Risk Score, a Blast Radius Score, risk factors, reason codes and recommended controls so your platform and your people can decide what happens next.
AI agents working with Salesforce may legitimately have access to customer records, CRM operations, exports, communications and administrative functions. Traditional permissions establish whether an agent CAN perform an operation. Asyrx adds another layer by evaluating the risk and potential impact of the specific proposed action before execution. Asyrx does not authorize, execute or block the action, and it does not replace Salesforce permissions or your enterprise IAM.
Identity
Who is acting?
Authorization
Can they perform the action?
Asyrx
What is the risk and potential impact of this particular action?
Where risk concentrates in Salesforce
Agent actions in Salesforce are not equally consequential
An agent may hold valid credentials and valid permissions for every action below. The difference between them is consequence, and that is what Asyrx assesses.
Customer and contact data movement
Exports of confidential CRM data — especially to destinations the agent has not used before — move regulated customer information outside the system of record.
Bulk record operations
Mass updates and deletions can touch tens of thousands of entities in a single proposed action, with limited practical reversibility in production.
Account and administrative changes
Configuration, ownership and administrative actions can alter how an entire revenue organization operates rather than one record.
Mass communications
Actions that contact large customer populations carry reputational and operational consequences that a permission check does not express.
Routine vs consequential
The same permission. A very different consequence.
Both assessments below come from the same central Asyrx assessment engine used by the API, applied to the same demonstration action model.
Routine action
Proposed action
Update 3 account status fields
Proposed by Customer Operations Agent · production
A routine status update on three accounts, consistent with the agent's daily behaviour.
Action Risk
10 / 100
Blast Radius
16 / 100
PRODUCTION_ENVIRONMENTRecommended control: No Additional Control Suggested
Confidence 80%. Asyrx recommends controls; it does not approve, deny, block or execute this action.
- Limited entity count — three records in scope.
- An expected part of the normal customer-operations workflow.
- No unusual or external destination involved.
- Low operational scope relative to the production org.
- Comparatively reversible field-level change.
Consequential action
Proposed action
Export 84,000 CRM contacts
Proposed by Customer Operations Agent · production
The agent proposes exporting the full contact database to a new external analytics destination.
Action Risk
60 / 100
Blast Radius
97 / 100
NOVEL_DESTINATIONHIGH_ENTITY_COUNTSENSITIVE_DATA_EXPORTPRODUCTION_ENVIRONMENTRecommended control: Secondary Approval Recommended
Confidence 83%. Asyrx recommends controls; it does not approve, deny, block or execute this action.
High-impact scenarios
Consequential Salesforce actions Asyrx is built to evaluate
Each scenario is a demonstration input assessed by the central engine. No action is performed in any target system from this page.
Proposed action
Export 84,000 CRM contacts
Proposed by Customer Operations Agent · production
The agent proposes exporting the full contact database to a new external analytics destination.
Action Risk
60 / 100
Blast Radius
97 / 100
NOVEL_DESTINATIONHIGH_ENTITY_COUNTSENSITIVE_DATA_EXPORTPRODUCTION_ENVIRONMENTRecommended control: Secondary Approval Recommended
Confidence 83%. Asyrx recommends controls; it does not approve, deny, block or execute this action.
Proposed action
Delete 25,000 customer records
Proposed by Customer Operations Agent · production
A deduplication workflow proposes a bulk deletion against production CRM records.
Action Risk
80 / 100
Blast Radius
96 / 100
DESTRUCTIVE_ACTIONLOW_REVERSIBILITYHIGH_ENTITY_COUNTPRODUCTION_ENVIRONMENTLARGE_OPERATIONAL_IMPACTSENSITIVE_DATARecommended control: Secondary Approval Recommended
Confidence 80%. Asyrx recommends controls; it does not approve, deny, block or execute this action.
Action Risk and Blast Radius
Two separate measurements, never merged
Action Risk asks how concerning the proposed action is given its context. Blast Radius asks how much potential impact could occur if the action were wrong, compromised, unintended or inappropriate. Asyrx also returns risk level, confidence, risk factors, reason codes, behavioral context, policy context and recommended controls.
Example assessment — Export 84,000 CRM contacts
Action Risk Score
How concerning is this proposed action in its context?
Blast Radius Score
How far could impact spread if the action were wrong, compromised or unintended?
Blast radius dimensions
No direct monetary value attached to this action.
84,000 record(s) or entities in scope.
Data classified as confidential leaving the system of record.
Targets a production environment with live operational dependencies.
No permission or credential change detected.
Reversibility assessed as partially reversible.
Integration architecture
Where Asyrx sits in a Salesforce agent workflow
Asyrx is called before your system executes the action. It returns intelligence; it never reaches into the target system.
- 01
AI agent
Your agent or orchestrator prepares an action.
- 02
Proposed action
Normalized into the Asyrx action model.
- 03
Asyrx Action Assessment API
Assesses the proposed action. It does not execute it.
- 04
Action Risk · Blast Radius · Reason Codes · Recommended Controls
Structured intelligence returned in-line.
- 05
Your system or human reviewer
Your policy layer and people evaluate.
- 06
You determine what happens
Authorization and execution stay with you.
Asyrx is a pre-execution assessment step. Your platform submits the normalized proposed action, receives the assessment in-line, and applies your own policy — hold for review, require secondary approval, reduce scope or proceed. Asyrx is a use-case integration pattern for actions involving Salesforce; it is not a Salesforce partnership, certification or endorsement, and there is no one-click Salesforce connection.
Business value
What enterprises can do with Salesforce action intelligence
- Distinguish routine CRM automation from consequential operations.
- Identify unusual action scope before it executes.
- Identify sensitive-data movement out of the system of record.
- Identify novel destinations for customer data.
- Evaluate potentially destructive record operations.
- Create explainable, reviewable assessment records.
- Complement Salesforce permissions and enterprise IAM.
- Preserve customer-controlled authorization and execution.
Asyrx provides decision-support intelligence. It does not guarantee prevention of any incident, and it does not replace Salesforce permissions, your IAM, your authorization layer or human approval.
Developer example
One assessment call before execution
POST /api/v1/actions/assess — Salesforce
{
"agent_key": "agt_customer_ops",
"target_system": "salesforce",
"action_type": "contacts.export",
"environment": "production",
"entities_affected": 84000,
"records_affected": 84000,
"data_classification": "confidential",
"destination": "analytics-vendor-staging.example.com",
"reversibility": "partially_reversible",
"production_impact": true,
"action_description": "Export 84,000 CRM contacts to an external analytics destination."
}These are the actual fields accepted by the Asyrx Action Assessment API. Only action_type and environment are required; the remaining context improves the assessment. Asyrx never connects to your Salesforce org — your platform submits the normalized proposed action.