unshare_commitment
Stop sharing a commitment with someone. Removes their access. [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/unshare-commitment.md
What unshare_commitment does on Freedom Mcp
AI agents use unshare_commitment 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 | — | FreedomOS company id to act within (you must be a member). Required for company-scoped tools. |
title_search | string | — | Search by title if ID not known (fuzzy match) |
commitment_id | string | — | The UUID of the commitment to unshare |
unshare_email | string | Yes | Email address of the person to remove sharing for |
Parameters from the server's own tool schema.
Why unshare_commitment is rated Medium
This tool modifies access control by removing someone's ability to view or interact with a commitment. While it changes state and has organizational impact, the action is reversible (re-sharing is possible), distinguishing it from Destructive. It does not delete the commitment itself, only revokes access.
From the tool's definition Tool description: 'Stop sharing a commitment with someone. Removes their access.' The verb 'removes' indicates a modification (access revocation) that is reversible—access can be re-granted.
Attacks that exploit this kind of access
The rule that runs unshare_commitment 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 unshare_commitment, this is the rule to start with:
unshare_commitment 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 unshare_commitment call is checked against it from then on.
Questions about unshare_commitment
Stop sharing a commitment with someone. Removes their access. [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.
unshare_commitment accepts 4 parameters: companyId, title_search, commitment_id, unshare_email. Required: unshare_email. 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 unshare_commitment: 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.
unshare_commitment 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 unshare_commitment 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 unshare_commitment. 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.
unshare_commitment 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