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

remove_agent_activity

Retire ONE activity from an agent's plan. Soft-archive (recoverable): the activity is MOVED to jd_content.archived_activities and removed from the live plan, so the agent stops running it. Never hard-deletes. [sensitive-tier — first use may require a manager's approval; a from-now-on approval mak...

SERVERFreedom Mcp SOURCEhttps://twuluxmoognlwtmaoqgo.supabase.co/functions/v1/freedom-mcp
Critical RISK CLASS
Category Destructive
Parameters 61 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-getfreedomos-freedom-mcp/remove-agent-activity.md

What remove_agent_activity does on Freedom Mcp

AI agents call remove_agent_activity to permanently remove resources in Freedom Mcp, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

ParameterTypeRequiredDescription
reason string Optional reason for retiring (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 EXACT (case-insensitive) name of the activity to retire. Provide this or activity_index.
activity_index number 0-based index into the activity plan. Alternative to activity_name.

Parameters from the server's own tool schema.

Why remove_agent_activity is rated Critical

Removes activity from agent's live plan; though soft-archived, it irreversibly halts agent execution.

From the tool's definition removed from the live plan, agent stops running it, MOVED to archived

Questions about remove_agent_activity

What does the remove_agent_activity tool do? +

Retire ONE activity from an agent's plan. Soft-archive (recoverable): the activity is MOVED to jd_content.archived_activities and removed from the live plan, so the agent stops running it. Never hard-deletes. [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 Destructive tool in the Freedom Mcp MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

What parameters does remove_agent_activity accept? +

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

How do I enforce a policy on remove_agent_activity? +

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

remove_agent_activity is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit remove_agent_activity? +

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

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

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