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 security permissions (Field Level Security), which is a reversible write operation. While permission changes have significant blast radius if misused by an AI agent (could grant/revoke access inappropriately across profiles), the operations themselves are not destructive (can be undone), financial, or code execution.
From the tool's definition Tool description states it can 'Grant or revoke read/edit access' and 'Bulk update permissions for multiple profiles', which are reversible modifications to field-level security settings.
Risk signalsAdmin/system-level operation
Documented attack patterns abuse exactly the kind of access salesforce_manage_field_permissions gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Salesforce MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for salesforce_manage_field_permissions:
{
"version": "1",
"default": "deny",
"tools": {
"salesforce_manage_field_permissions": {
"limits": [
{
"counter": "salesforce_manage_field_permissions_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}salesforce_manage_field_permissions 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.
Free to start. No card required.
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 (tsmztech/mcp-server-salesforce). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 8 Salesforce MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
8 Salesforce MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.