update_agent_activity
Edit ONE existing activity in an agent's plan — change its name, description, frequency, tools_used, deliverable, or completion_criteria. Surgical alternative to regenerating the whole plan. [sensitive-tier — first use may require a manager's approval; a from-now-on approval makes future calls se...
This record as markdown: /tools/com-getfreedomos-freedom-mcp/update-agent-activity.md
What update_agent_activity does on Freedom Mcp
AI agents use update_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.
| Parameter | Type | Required | Description |
|---|---|---|---|
patch | object | Yes | Fields to change. Only the supplied fields are updated. |
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 edit. 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 update_agent_activity is rated Medium
This tool creates or modifies data (an agent's activity record) in a way that is reversible and non-destructive. It allows changes to workflow metadata and planning documents but does not execute external operations, delete data irreversibly, or move money. The sensitive-tier approval requirement indicates organizational awareness of modification risk, supporting medium severity.
From the tool's definition 'Edit ONE existing activity in an agent's plan — change its name, description, frequency, tools_used, deliverable, or completion_criteria.' The tool modifies existing plan records reversibly without deletion or financial impact.
Risk signalsHigh parameter count (16 properties)
Attacks that exploit this kind of access
The rule that runs update_agent_activity safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Freedom Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_agent_activity, this is the rule to start with:
update_agent_activity stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Freedom Mcp, apply this rule, and every update_agent_activity call is checked against it from then on.
Questions about update_agent_activity
Edit ONE existing activity in an agent's plan — change its name, description, frequency, tools_used, deliverable, or completion_criteria. Surgical alternative to regenerating the whole plan. [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.
update_agent_activity accepts 6 parameters: patch, agent_id, companyId, agent_name, activity_name, activity_index. Required: patch, companyId. The full parameter table on this page comes from the server's own tool schema.
Register the Freedom MCP server in PolicyLayer and add a rule for update_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.
update_agent_activity is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_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.
Set action: deny in the PolicyLayer policy for update_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.
update_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.
This server
Across the catalogue