New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

toggle_agent_schedule

Pause or resume an agent's scheduled activities — the whole activity plan, or a single activity via activity_name. Pausing stops future scheduler-dispatched runs until resumed; manual trigger_agent_activity still works and in-flight runs are not affected. [sensitive-tier, initiates a multi-step a...

SERVERFreedom Mcp SOURCEhttps://twuluxmoognlwtmaoqgo.supabase.co/functions/v1/freedom-mcp
High RISK CLASS
Category Execute
Parameters 43 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-getfreedomos-freedom-mcp/toggle-agent-schedule.md

What toggle_agent_schedule does on Freedom Mcp

AI agents invoke toggle_agent_schedule to trigger actions in Freedom 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.

ParameterTypeRequiredDescription
action string Yes pause or resume
companyId string Yes FreedomOS company id to act within (you must be a member). Required for company-scoped tools.
agent_name string Yes Name of the agent whose schedule to toggle
activity_name string Optional: pause/resume only this one activity (exact name, case-insensitive). Omit to affect the agent's whole activity plan.

Parameters from the server's own tool schema.

Why toggle_agent_schedule is rated High

Toggling agent schedules triggers or halts automated multi-step agent processes with operational impact.

From the tool's definition Pause or resume an agent's scheduled activities; initiates a multi-step agent process

Questions about toggle_agent_schedule

What does the toggle_agent_schedule tool do? +

Pause or resume an agent's scheduled activities — the whole activity plan, or a single activity via activity_name. Pausing stops future scheduler-dispatched runs until resumed; manual trigger_agent_activity still works and in-flight runs are not affected. [sensitive-tier, initiates a multi-step agent process — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.]. It is categorised as a Execute tool in the Freedom Mcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does toggle_agent_schedule accept? +

toggle_agent_schedule accepts 4 parameters: action, companyId, agent_name, activity_name. Required: action, companyId, agent_name. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on toggle_agent_schedule? +

Register the Freedom MCP server in PolicyLayer and add a rule for toggle_agent_schedule: 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 Freedom Mcp. Nothing to install.

What risk level is toggle_agent_schedule? +

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

Can I rate-limit toggle_agent_schedule? +

Yes. Add a rate_limit block to the toggle_agent_schedule 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 toggle_agent_schedule completely? +

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

toggle_agent_schedule is provided by the Freedom MCP server (https://twuluxmoognlwtmaoqgo.supabase.co/functions/v1/freedom-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Freedom, 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 Freedom'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.