remove_dashboard_widget
Remove a widget from an agent dashboard. [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.]
This record as markdown: /tools/com-getfreedomos-freedom-mcp/remove-dashboard-widget.md
What remove_dashboard_widget does on Freedom Mcp
AI agents call remove_dashboard_widget 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
companyId | string | Yes | FreedomOS company id to act within (you must be a member). Required for company-scoped tools. |
widget_id | string | Yes | UUID of the widget to remove |
Parameters from the server's own tool schema.
Why remove_dashboard_widget is rated Critical
Removing a dashboard widget is an irreversible deletion of a configured UI element.
From the tool's definition Remove a widget from an agent dashboard
Attacks that exploit this kind of access
The rule that runs remove_dashboard_widget 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 remove_dashboard_widget, this is the rule to start with:
remove_dashboard_widget is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Freedom Mcp, apply this rule, and every remove_dashboard_widget call is checked against it from then on.
Questions about remove_dashboard_widget
Remove a widget from an agent dashboard. [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 Destructive tool in the Freedom Mcp MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
remove_dashboard_widget accepts 2 parameters: companyId, widget_id. Required: companyId, widget_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 remove_dashboard_widget: 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.
remove_dashboard_widget is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove_dashboard_widget 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 remove_dashboard_widget. 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.
remove_dashboard_widget 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.
Across the catalogue