update_agent

SERVERFreedom Mcp SOURCEhttps://twuluxmoognlwtmaoqgo.supabase.co/functions/v1/freedom-mcp

Medium RISK CLASS

Category Write

Parameters 42 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/update-agent.md

WHAT IT DOES

What update_agent does on Freedom Mcp

AI agents use update_agent 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
`name`	string	—	New display name — a single first name (e.g. "Garth"). Omit to leave the name unchanged.
`role`	string	—	New role / job title (e.g. "Agent Deployment & Quality Reviewer"). Do NOT include the agent name. Omit to leave the role unchanged.
`agent_id`	string	Yes	UUID of the agent to update. Use get_team_roster to find IDs.
`companyId`	string	Yes	FreedomOS company id to act within (you must be a member). Required for company-scoped tools.

Parameters from the server's own tool schema.

RISK

Why update_agent is rated Medium

This tool modifies agent records by changing display names and job titles—classic Write operations. The changes are reversible (you can rename again). It does not delete data (not Destructive), execute arbitrary code (not Execute), nor move money (not Financial).

From the tool's definition Updates an agent's display name and/or role/job-title. Explicitly described as modifying (renaming, fixing) agent metadata, which is a reversible write operation.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs update_agent 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, this is the rule to start with:

update_agent Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_agent": {
      "limits": [
        {
          "counter": "update_agent_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Freedom Mcp, apply this rule, and every update_agent call is checked against it from then on.

FAQ

Questions about update_agent

What does the update_agent tool do? +

Rename a team member or fix its role/title. Updates an agent's display name and/or role/job-title. Use when the user says "rename X to Y", "call this agent Z", or "fix the title". For changing an agent's mission/skills use recalibrate_agent_jd instead. [write-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 update_agent accept? +

update_agent accepts 4 parameters: name, role, agent_id, companyId. Required: agent_id, companyId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on update_agent? +

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

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

Can I rate-limit update_agent? +

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

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

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

KEEP EXPLORING

More on Freedom, and thousands of servers like it.

This server

All 238 Freedom tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_kill_agent on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →