sf_create_scheduled_job
Schedules an Apex class that implements the Schedulable interface to run on a cron schedule. Use for batch processing, nightly data cleanup, report generation, or any periodic automation. The Apex class must already exist in the org. Example cron:
This record as markdown: /tools/io-github-semwalajay83-sem-salesforce-metadata-mcp/sf-create-scheduled-job.md
What sf_create_scheduled_job does on Salesforce Metadata Mcp
AI agents invoke sf_create_scheduled_job 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_scheduled_job is rated High
This tool schedules Apex code to execute automatically on a recurring schedule. It triggers external code execution (Apex) that can perform data modifications, deletions, or other operations depending on the scheduled class. The blast radius is high because a misconfigured schedule could repeatedly run destructive or unintended operations (e.g., 'nightly data cleanup') across the entire org.
From the tool's definition Schedules an Apex class that implements the Schedulable interface to run on a cron schedule... batch processing, nightly data cleanup, report generation, or any periodic automation
Attacks that exploit this kind of access
The rule that runs sf_create_scheduled_job 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_scheduled_job, this is the rule to start with:
sf_create_scheduled_job stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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_scheduled_job call is checked against it from then on.
Questions about sf_create_scheduled_job
Schedules an Apex class that implements the Schedulable interface to run on a cron schedule. Use for batch processing, nightly data cleanup, report generation, or any periodic automation. The Apex class must already exist in the org. Example cron:. 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.
Register the Salesforce Metadata MCP server in PolicyLayer and add a rule for sf_create_scheduled_job: 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_scheduled_job is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the sf_create_scheduled_job 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_scheduled_job. 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_scheduled_job 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.
Across the catalogue