set_revenue_channels

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

Medium RISK CLASS

Category Write

Parameters 32 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/set-revenue-channels.md

WHAT IT DOES

What set_revenue_channels does on Freedom Mcp

AI agents use set_revenue_channels 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
`channels`	array	Yes	Any that apply: stripe, xero, shopify, amazon, ebay, manual, none_yet, other. "none_yet" is exclusive — if the business is pre-revenue, pass ONLY ["none_yet"].
`companyId`	string	Yes	FreedomOS company id to act within (you must be a member). Required for company-scoped tools.
`other_label`	string	—	Required when channels includes "other" — the operator's own words for the revenue channel (e.g. "wholesale invoices").

Parameters from the server's own tool schema.

RISK

Why set_revenue_channels is rated Medium

This tool creates or modifies configuration data (revenue channel declarations) that persists and influences agent behavior and system routing. It is reversible (can be updated when 'operator says it changed') and does not delete data, move money, or execute arbitrary code, making Write the appropriate category.

From the tool's definition Tool description states it "Declare[s] where this business makes money" and "Once declared, agents stop asking" — this modifies system state that affects downstream routing and agent behavior.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

set_revenue_channels Rate-limited

set_revenue_channels 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": {
    "set_revenue_channels": {
      "limits": [
        {
          "counter": "set_revenue_channels_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 set_revenue_channels call is checked against it from then on.

FAQ

Questions about set_revenue_channels

What does the set_revenue_channels tool do? +

Declare where this business makes money — stripe, xero, shopify, amazon, ebay, manual invoicing, "none_yet" (pre-revenue), or other (name it). This is OPERATOR TRUTH an agent cannot derive, so it is gated: an autonomous agent CANNOT declare it — only a human (chat) or a graduated MCP operator can. Once declared, agents stop asking to connect Stripe for businesses that don't use it and are routed to the right revenue tool for this company's actual channel(s). Call get_setup_state first — if "Revenue channels" already shows done, only call this again when the operator says it changed. [sensitive-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 set_revenue_channels accept? +

set_revenue_channels accepts 3 parameters: channels, companyId, other_label. Required: channels, companyId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on set_revenue_channels? +

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

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

Can I rate-limit set_revenue_channels? +

Yes. Add a rate_limit block to the set_revenue_channels 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 set_revenue_channels completely? +

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

set_revenue_channels 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

emit_assumption_set on 0sec →set-prioity on Kanban MCP Server →team_manager_set_sources on Team Manager MCP → The MCP Attack Database →

Guides

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