list_commitments
List the user's active commitments. Shows what's on their plate across all life domains, sorted by due date.
This record as markdown: /tools/com-getfreedomos-freedom-mcp/list-commitments.md
What list_commitments does on Freedom Mcp
AI agents call list_commitments to retrieve information from Freedom Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
domain | string | — | Filter by domain (optional). E.g., "family", "home", "company:acme" |
companyId | string | — | FreedomOS company id to act within (you must be a member). Required for company-scoped tools. |
include_completed | boolean | — | Include completed commitments (default: false) |
Parameters from the server's own tool schema.
Why list_commitments is rated Low
This tool retrieves and displays existing commitment data sorted by due date. It has no side effects, does not modify or delete data, and does not execute external operations. It is a straightforward read operation that queries a data store and returns results to the user.
From the tool's definition Tool name 'list_commitments' and description 'List the user's active commitments' — uses the verb 'list', which is a read-only query operation. Description explicitly states it 'shows' data with no mention of modification, deletion, or execution.
Attacks that exploit this kind of access
The rule that runs list_commitments 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 list_commitments, this is the rule to start with:
list_commitments is read-only, so it stays allowed. 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 list_commitments call is checked against it from then on.
Questions about list_commitments
List the user's active commitments. Shows what's on their plate across all life domains, sorted by due date. It is categorised as a Read tool in the Freedom Mcp MCP Server, which means it retrieves data without modifying state.
list_commitments accepts 3 parameters: domain, companyId, include_completed. 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 list_commitments: 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.
list_commitments is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_commitments 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 list_commitments. 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.
list_commitments 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