Manage Field Level Security (Field Permissions) for custom and standard fields. - Grant or revoke read/edit access to fields for specific profiles or permission sets - View current field permissions - Bulk update permissions for multiple profiles Examples: 1. Grant System Administrator access to ...
AI agents use salesforce_manage_field_permissions to create or update resources in Salesforce MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Salesforce MCP Server environment.
This tool modifies field-level security permissions, which controls who can access sensitive data fields. While the changes are reversible (Write rather than Destructive), the blast radius is high because improper use could grant unauthorized access to sensitive fields across multiple profiles, expose confidential data fields to unintended users, or revoke legitimate access.
From the tool's definition The tool description explicitly states it can 'Grant or revoke read/edit access to fields for specific profiles or permission sets' and perform 'Bulk update permissions for multiple profiles.' These are reversible modifications to system configuration and…
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
Manage Field Level Security (Field Permissions) for custom and standard fields. - Grant or revoke read/edit access to fields for specific profiles or permission sets - View current field permissions - Bulk update permissions for multiple profiles Examples: 1. Grant System Administrator access to a field 2. Give read-only access to a field for specific profiles 3. Check which profiles have access to a field. It is categorised as a Write tool in the Salesforce MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Salesforce MCP Server MCP server in PolicyLayer and add a rule for salesforce_manage_field_permissions: 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 Server. Nothing to install.
salesforce_manage_field_permissions is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the salesforce_manage_field_permissions 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 salesforce_manage_field_permissions. 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.
salesforce_manage_field_permissions is provided by the Salesforce MCP Server MCP server (jeresalguero30/mcp-server-salesforce). 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 →