reassign_reports
Reassign all scheduled reports from one agent to another. Use when user says "reassign reports", "transfer reports to [agent]", "move reports from [agent] to [agent]". Useful after deactivating an agent or hiring a replacement. [write-tier — first use may require a manager's approval; a from-now-...
This record as markdown: /tools/com-getfreedomos-freedom-mcp/reassign-reports.md
What reassign_reports does on Freedom Mcp
AI agents use reassign_reports 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 |
|---|---|---|---|
companyId | string | Yes | FreedomOS company id to act within (you must be a member). Required for company-scoped tools. |
to_agent_id | string | Yes | UUID of the agent to transfer reports TO |
from_agent_id | string | Yes | UUID of the agent to transfer reports FROM |
Parameters from the server's own tool schema.
Why reassign_reports is rated Medium
This tool modifies metadata/assignments (which agent owns reports) rather than deleting or creating reports themselves. It is reversible: reports can be reassigned back. While it affects operational workflows, there is no financial impact, code execution, or data destruction. Write tier with potential manager approval gate is appropriate for this class of change.
From the tool's definition Tool description explicitly states it 'reassign[s]' and 'transfer[s]' reports from one agent to another, modifying the assignment state of scheduled reports. The write-tier annotation confirms it creates reversible changes.
Attacks that exploit this kind of access
The rule that runs reassign_reports 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 reassign_reports, this is the rule to start with:
reassign_reports 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 reassign_reports call is checked against it from then on.
Questions about reassign_reports
Reassign all scheduled reports from one agent to another. Use when user says "reassign reports", "transfer reports to [agent]", "move reports from [agent] to [agent]". Useful after deactivating an agent or hiring a replacement. [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.
reassign_reports accepts 3 parameters: companyId, to_agent_id, from_agent_id. Required: companyId, to_agent_id, from_agent_id. 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 reassign_reports: 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.
reassign_reports 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 reassign_reports 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 reassign_reports. 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.
reassign_reports 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