trigger_agent_activity
Trigger a specific agent to run a specific activity immediately. This dispatches the work and returns — it does not wait for the activity to complete. Use this to direct agents to take action. [sensitive-tier, initiates a multi-step agent process — first use may require a manager's approval; a fr...
This record as markdown: /tools/com-getfreedomos-freedom-mcp/trigger-agent-activity.md
What trigger_agent_activity does on Freedom Mcp
AI agents invoke trigger_agent_activity to trigger actions in Freedom Mcp. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
reason | string | — | Optional. A specific instruction for THIS run only — e.g. "only reconcile the X reply queue, skip everything else". When given, it becomes this run's goal and t |
companyId | string | Yes | FreedomOS company id to act within (you must be a member). Required for company-scoped tools. |
agent_name | string | Yes | Name of the agent to trigger (e.g. "Aiko") |
activity_name | string | Yes | Name of the activity to run (e.g. "weekly_content_report") |
Parameters from the server's own tool schema.
Why trigger_agent_activity is rated High
This tool executes arbitrary agent activities with real business consequences (per the server context: finance, OKRs, customer scoring). While it doesn't directly modify data or delete, it triggers multi-step processes external to the caller whose outcomes cannot be fully predicted. The approval gate indicates organizational risk.
From the tool's definition 'Trigger a specific agent to run a specific activity immediately' and 'dispatches the work' — directly initiates external agent operations whose effects depend on which agent and activity are specified.
Attacks that exploit this kind of access
The rule that runs trigger_agent_activity 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 trigger_agent_activity, this is the rule to start with:
trigger_agent_activity stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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 trigger_agent_activity call is checked against it from then on.
Questions about trigger_agent_activity
Trigger a specific agent to run a specific activity immediately. This dispatches the work and returns — it does not wait for the activity to complete. Use this to direct agents to take action. [sensitive-tier, initiates a multi-step agent process — 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 Execute tool in the Freedom Mcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
trigger_agent_activity accepts 4 parameters: reason, companyId, agent_name, activity_name. Required: companyId, agent_name, activity_name. 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 trigger_agent_activity: 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.
trigger_agent_activity is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the trigger_agent_activity 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 trigger_agent_activity. 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.
trigger_agent_activity 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.
Across the catalogue