sf_create_apex_test_class

Creates and deploys an Apex Test Class (annotated with @isTest). Provide the full test class source code. Optionally run the tests immediately after deployment. Test classes are required for Salesforce deployments to production (minimum 75% code coverage). Use for unit testing Apex classes, trigg...

SERVERSalesforce Metadata Mcp SOURCEsalesforce-metadata-mcp
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-semwalajay83-sem-salesforce-metadata-mcp/sf-create-apex-test-class.md

What sf_create_apex_test_class does on Salesforce Metadata Mcp

AI agents invoke sf_create_apex_test_class to trigger actions in Salesforce Metadata Mcp. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Why sf_create_apex_test_class is rated High

This tool both writes (creates and deploys code to a Salesforce org) and executes (runs tests immediately after deployment). Since it deploys and can execute Apex code on the org, Execute is the most severe applicable category. Misuse could deploy malicious test code or trigger unintended side effects via test execution in a production environment.

From the tool's definition Creates and deploys an Apex Test Class... Optionally run the tests immediately after deployment.

Questions about sf_create_apex_test_class

What does the sf_create_apex_test_class tool do? +

Creates and deploys an Apex Test Class (annotated with @isTest). Provide the full test class source code. Optionally run the tests immediately after deployment. Test classes are required for Salesforce deployments to production (minimum 75% code coverage). Use for unit testing Apex classes, triggers, and business logic. It is categorised as a Execute tool in the Salesforce Metadata Mcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on sf_create_apex_test_class? +

Register the Salesforce Metadata MCP server in PolicyLayer and add a rule for sf_create_apex_test_class: 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.

What risk level is sf_create_apex_test_class? +

sf_create_apex_test_class is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit sf_create_apex_test_class? +

Yes. Add a rate_limit block to the sf_create_apex_test_class 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.

How do I block sf_create_apex_test_class completely? +

Set action: deny in the PolicyLayer policy for sf_create_apex_test_class. 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.

What MCP server provides sf_create_apex_test_class? +

sf_create_apex_test_class 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Salesforce Metadata's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.