recalibrate_agent_jd
Regenerate an agent's JD using fresh company context. Updates mission, expertise, guardrails, success metrics, and optionally activity plans. Works for both hired agents and Linnet. Use when the company has evolved, an agent needs recalibration, or the user wants to refine an agent's direction. [...
This record as markdown: /tools/com-getfreedomos-freedom-mcp/recalibrate-agent-jd.md
What recalibrate_agent_jd does on Freedom Mcp
AI agents use recalibrate_agent_jd 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 |
|---|---|---|---|
agent_id | string | Yes | UUID of the agent to recalibrate. 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. |
focus_areas | string | — | Optional user guidance for recalibration, e.g. "focus more on SEO" or "add financial analysis" |
regenerate_activities | boolean | — | Also regenerate the activity plan (default: false — preserves evolved activities) |
Parameters from the server's own tool schema.
Why recalibrate_agent_jd is rated Medium
This tool creates or modifies agent job descriptions, mission statements, and operational guardrails—reversible changes to data structures governing agent behavior. While it could influence agent execution downstream, the direct action is configuration modification (Write), not code execution or financial transactions.
From the tool's definition The tool 'regenerate an agent's JD' and 'Updates mission, expertise, guardrails, success metrics, and optionally activity plans' indicates modification of agent configuration and operational parameters.
Attacks that exploit this kind of access
The rule that runs recalibrate_agent_jd 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 recalibrate_agent_jd, this is the rule to start with:
recalibrate_agent_jd 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 recalibrate_agent_jd call is checked against it from then on.
Questions about recalibrate_agent_jd
Regenerate an agent's JD using fresh company context. Updates mission, expertise, guardrails, success metrics, and optionally activity plans. Works for both hired agents and Linnet. Use when the company has evolved, an agent needs recalibration, or the user wants to refine an agent's direction. [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.
recalibrate_agent_jd accepts 4 parameters: agent_id, companyId, focus_areas, regenerate_activities. Required: agent_id, 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 recalibrate_agent_jd: 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.
recalibrate_agent_jd 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 recalibrate_agent_jd 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 recalibrate_agent_jd. 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.
recalibrate_agent_jd 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