sf_assign_queue_member
Adds a user to an existing Queue (GroupMember SObject) by username and queue DeveloperName. The queue must already exist (create via sf_create_queue). Users in queues can be assigned records and receive queue notification emails.
This record as markdown: /tools/io-github-semwalajay83-sem-salesforce-metadata-mcp/sf-assign-queue-member.md
What sf_assign_queue_member does on Salesforce Metadata Mcp
AI agents use sf_assign_queue_member to create or update resources in Salesforce Metadata Mcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Salesforce Metadata Mcp environment.
Why sf_assign_queue_member is rated Medium
This tool modifies organizational state by creating a new GroupMember association, which is a reversible write operation. It adds a user to a queue, enabling them to receive record assignments and notifications. This is not destructive (reversible via removal), not financial, and not execute (no arbitrary code/command execution).
From the tool's definition Adds a user to an existing Queue (GroupMember SObject) by username and queue DeveloperName. Users in queues can be assigned records and receive queue notification emails.
Attacks that exploit this kind of access
The rule that runs sf_assign_queue_member safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Salesforce Metadata Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For sf_assign_queue_member, this is the rule to start with:
sf_assign_queue_member 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Salesforce Metadata Mcp, apply this rule, and every sf_assign_queue_member call is checked against it from then on.
Questions about sf_assign_queue_member
Adds a user to an existing Queue (GroupMember SObject) by username and queue DeveloperName. The queue must already exist (create via sf_create_queue). Users in queues can be assigned records and receive queue notification emails. It is categorised as a Write tool in the Salesforce Metadata Mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Salesforce Metadata MCP server in PolicyLayer and add a rule for sf_assign_queue_member: 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 Metadata Mcp. Nothing to install.
sf_assign_queue_member 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 sf_assign_queue_member 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 sf_assign_queue_member. 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.
sf_assign_queue_member is provided by the Salesforce Metadata MCP server (salesforce-metadata-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Salesforce Metadata, and thousands of servers like it.
This server
Across the catalogue