sf_create_apex_email_service
Creates an Apex Email Service that processes inbound emails via an Apex class implementing Messaging.InboundEmailHandler. Useful for creating support cases from emails, parsing email content, or triggering workflows from inbound messages. The Apex class must exist before creating the service.
This record as markdown: /tools/io-github-semwalajay83-sem-salesforce-metadata-mcp/sf-create-apex-email-service.md
What sf_create_apex_email_service does on Salesforce Metadata Mcp
AI agents use sf_create_apex_email_service 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_create_apex_email_service is rated Medium
The tool creates a new Salesforce metadata component (an Email Service) that connects an Apex class to inbound email processing. This is a Write operation because it creates new metadata configuration. Severity is high because misconfiguration could cause emails to be processed incorrectly, potentially triggering unintended workflows, creating unwanted support cases, or executing unintended business logic.
From the tool's definition Creates an Apex Email Service that processes inbound emails via an Apex class. This tool creates new configuration that sets up email processing logic, which is a reversible data modification operation in Salesforce metadata.
Attacks that exploit this kind of access
The rule that runs sf_create_apex_email_service 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_create_apex_email_service, this is the rule to start with:
sf_create_apex_email_service 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_create_apex_email_service call is checked against it from then on.
Questions about sf_create_apex_email_service
Creates an Apex Email Service that processes inbound emails via an Apex class implementing Messaging.InboundEmailHandler. Useful for creating support cases from emails, parsing email content, or triggering workflows from inbound messages. The Apex class must exist before creating the service. 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_create_apex_email_service: 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_create_apex_email_service 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_create_apex_email_service 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_create_apex_email_service. 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_create_apex_email_service 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