manage_responsibilities

SERVERFreedom Mcp SOURCEhttps://twuluxmoognlwtmaoqgo.supabase.co/functions/v1/freedom-mcp

Medium RISK CLASS

Category Write

Parameters 72 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-getfreedomos-freedom-mcp/manage-responsibilities.md

WHAT IT DOES

What manage_responsibilities does on Freedom Mcp

AI agents use manage_responsibilities 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
`action`	string	Yes	Action to perform
`reason`	string	—	Why the change is happening (e.g., "vacation", "new hire", "role change")
`domains`	array	—	Domain names to assign (e.g., ["marketing", "content", "social"]). Use lowercase.
`companyId`	string	Yes	FreedomOS company id to act within (you must be a member). Required for company-scoped tools.
`valid_until`	string	—	ISO date string when delegation expires. Only for delegate action. Omit for permanent assignments.
`target_user_email`	string	—	Email of the user to assign/delegate to. Required for assign and delegate.
`delegation_from_email`	string	—	Email of the user delegating their responsibilities. Only for delegate action.

Parameters from the server's own tool schema.

RISK

Why manage_responsibilities is rated Medium

This tool modifies organizational structure and information routing by changing who receives agent output for specific domains. While reversible (characteristic of Write), the impact is high because misconfiguration could cause sensitive outputs (finance, marketing data) to route to unauthorized users, creating compliance and security risks.

From the tool's definition Tool performs 'Assign, delegate, or revoke responsibility domains for team members' — explicit write operations (assign, delegate, revoke) that modify role/routing configuration.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs manage_responsibilities 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 manage_responsibilities, this is the rule to start with:

manage_responsibilities Rate-limited

manage_responsibilities 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "manage_responsibilities": {
      "limits": [
        {
          "counter": "manage_responsibilities_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Freedom Mcp, apply this rule, and every manage_responsibilities call is checked against it from then on.

FAQ

Questions about manage_responsibilities

What does the manage_responsibilities tool do? +

Assign, delegate, or revoke responsibility domains for team members. This controls routing — which user receives agent output for specific domains like marketing, finance, etc. [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.

What parameters does manage_responsibilities accept? +

manage_responsibilities accepts 7 parameters: action, reason, domains, companyId, valid_until, target_user_email, delegation_from_email. Required: action, companyId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on manage_responsibilities? +

Register the Freedom MCP server in PolicyLayer and add a rule for manage_responsibilities: 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.

What risk level is manage_responsibilities? +

manage_responsibilities is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit manage_responsibilities? +

Yes. Add a rate_limit block to the manage_responsibilities 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.

How do I block manage_responsibilities completely? +

Set action: deny in the PolicyLayer policy for manage_responsibilities. 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.

What MCP server provides manage_responsibilities? +

manage_responsibilities 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.

KEEP EXPLORING

More on Freedom, and thousands of servers like it.

This server

All 238 Freedom tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →