schedule_release
Schedule a release to publish at a specific time
Part of the Sanity MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
WHEN AI AGENTS USE THIS TOOL
AI agents invoke schedule_release to trigger processes or run actions in Sanity. Execute operations can have side effects beyond the immediate call — triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
WHY ENFORCE A POLICY ON SCHEDULE_RELEASE
schedule_release can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.
RECOMMENDED POLICY
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
tools:
schedule_release:
rules:
- action: allow
rate_limit:
max: 10
window: 60
validate:
required_args: trueSee the full Sanity policy for all 36 tools.
DETAILS
MORE SANITY TOOLS
publish_document Execute publish_release Execute get_initial_context Read get_sanity_config Read query_documents Read list_releases Read list_datasets Read get_schema Read SIMILAR EXECUTE TOOLS ON OTHER SERVERS
call-actor Apify boot_simulator Appium setup_wda Appium install_wda Appium auth0_deploy_action Auth0 auth0_publish_form Auth0 RELATED READING
FREQUENTLY ASKED QUESTIONS
What does the schedule_release tool do?
Schedule a release to publish at a specific time. It is categorised as a Execute tool in the Sanity MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
How do I enforce a policy on schedule_release?
Add a rule in your Intercept YAML policy under the tools section for schedule_release. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Sanity MCP server.
What risk level is schedule_release?
schedule_release is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Can I rate-limit schedule_release?
Yes. Add a rate_limit block to the schedule_release rule in your Intercept 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 schedule_release completely?
Set action: deny in the Intercept policy for schedule_release. 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 schedule_release?
schedule_release is provided by the Sanity MCP server (@sanity/mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
ENFORCE POLICIES ON SANITY
Open source. One binary. Zero dependencies.