configure_dashboard
Create or update a widget on your agent dashboard. Use this to display key metrics, charts, tables, or timelines that help the user understand your work at a glance. Each call creates or updates one widget. [write-tier — first use may require a manager's approval; a from-now-on approval makes fut...
This record as markdown: /tools/com-getfreedomos-freedom-mcp/configure-dashboard.md
What configure_dashboard does on Freedom Mcp
AI agents use configure_dashboard 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 |
|---|---|---|---|
data | array | — | Data rows for chart/table/list/gantt widgets. Each item is an object. - chart: [{ label: "Jan", value: 100 }, ...] - table: [{ col1: "val", col2: "val" }, ...] |
title | string | Yes | Display title for the widget (e.g., "Monthly Revenue", "Content Pipeline") |
config | object | — | Widget configuration. Shape depends on widget_type: - metric: { value, previous_value, format ("number"|"currency"|"percent"|"text"), trend_direction ("up"|"dow |
position | number | — | Display order (0 = first, higher = later). Default: 0 |
companyId | string | Yes | FreedomOS company id to act within (you must be a member). Required for company-scoped tools. |
widget_id | string | — | UUID of existing widget to update. Omit to create a new widget. |
is_visible | boolean | — | Whether the widget is visible on the dashboard. Default: true |
widget_type | string | Yes | Type of widget to create |
Parameters from the server's own tool schema.
Why configure_dashboard is rated Medium
This tool modifies dashboard configuration by creating or updating widgets—typical write operations. The changes are reversible (widgets can be deleted or replaced), and the approval tier structure indicates organizational controls are in place. No code execution, data deletion, or financial impact occurs. Severity is low because dashboard modifications have minimal blast radius and are easily undone.
From the tool's definition Tool description: 'Create or update a widget on your agent dashboard.' The verbs 'create' and 'update' indicate reversible data modification.
Attacks that exploit this kind of access
The rule that runs configure_dashboard 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 configure_dashboard, this is the rule to start with:
configure_dashboard 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 configure_dashboard call is checked against it from then on.
Questions about configure_dashboard
Create or update a widget on your agent dashboard. Use this to display key metrics, charts, tables, or timelines that help the user understand your work at a glance. Each call creates or updates one widget. [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.
configure_dashboard accepts 8 parameters: data, title, config, position, companyId, widget_id, is_visible, widget_type. Required: title, companyId, widget_type. 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 configure_dashboard: 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.
configure_dashboard 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 configure_dashboard 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 configure_dashboard. 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.
configure_dashboard 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