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

split_agent_activity

Split ONE oversized activity into smaller activities (intake + finish) without regenerating the rest of the plan. Use when a run hit the continuation safety backstop while still progressing — the activity is bigger than one deliverable. [sensitive-tier — first use may require a manager's approval...

SERVERFreedom Mcp SOURCEhttps://twuluxmoognlwtmaoqgo.supabase.co/functions/v1/freedom-mcp
Medium RISK CLASS
Category Write
Parameters 62 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/split-agent-activity.md

What split_agent_activity does on Freedom Mcp

AI agents use split_agent_activity to create or update resources in Freedom Mcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Freedom Mcp environment.

ParameterTypeRequiredDescription
pieces array Optional precomputed replacement activities (name, frequency, description, …). When omitted, derived from the source.
reason string Optional reason recorded on the archive + audit log.
agent_id string UUID of the agent. Optional if agent_name is provided.
companyId string Yes FreedomOS company id to act within (you must be a member). Required for company-scoped tools.
agent_name string Name of the agent. Provide this or agent_id.
activity_name string Yes Exact (case-insensitive) name of the oversized activity to split.

Parameters from the server's own tool schema.

Why split_agent_activity is rated Medium

Modifies existing plan by splitting activities into smaller parts; reversible write operation.

From the tool's definition Split ONE oversized activity into smaller activities without regenerating

Questions about split_agent_activity

What does the split_agent_activity tool do? +

Split ONE oversized activity into smaller activities (intake + finish) without regenerating the rest of the plan. Use when a run hit the continuation safety backstop while still progressing — the activity is bigger than one deliverable. [sensitive-tier — 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 Write tool in the Freedom Mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does split_agent_activity accept? +

split_agent_activity accepts 6 parameters: pieces, reason, agent_id, companyId, agent_name, activity_name. Required: companyId, activity_name. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on split_agent_activity? +

Register the Freedom MCP server in PolicyLayer and add a rule for split_agent_activity: 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 split_agent_activity? +

split_agent_activity is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit split_agent_activity? +

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

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

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