request_attention_spawn

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

High RISK CLASS

Category Execute

Parameters 62 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/request-attention-spawn.md

WHAT IT DOES

What request_attention_spawn does on Freedom Mcp

AI agents invoke request_attention_spawn 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
`cwd`	string	—	Working directory on the operator machine (e.g. /Users/…/GitHub/freedom-ai). Prefer absolute paths they already use.
`goal`	string	Yes	One-line goal for the new session (1–500 chars).
`host`	string	Yes	Which builder to open: grok (Terminal) \| claude-desktop (Claude.app Code — preferred) \| claude-code (Terminal CLI)
`companyId`	string	—	FreedomOS company id to act within (you must be a member). Required for company-scoped tools.
`session_id`	string	—	Optional stable session id; default auto-derived from host + project.
`first_instruction`	string	—	Optional first work sticky delivered after the new session announces (imperative).

Parameters from the server's own tool schema.

RISK

Why request_attention_spawn is rated High

This tool's primary function is to execute external operations (launch local development environments, open terminals, execute directives) on the host machine. While it involves queueing (a data structure operation), its effect is spawning processes and executing code directives, making it Execute rather than Write. The mention of 'optional first directive' indicates the tool can receive code/commands to run.

From the tool's definition The tool 'spawns' new local coding sessions, opens Terminal, and can receive 'optional first directive' — this executes operations on the operator's machine, not merely writing data.

Risk signalsAccepts file system path (cwd) · Accepts URL/endpoint input (host)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

request_attention_spawn Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "request_attention_spawn": {
      "limits": [
        {
          "counter": "request_attention_spawn_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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 request_attention_spawn call is checked against it from then on.

FAQ

Questions about request_attention_spawn

What does the request_attention_spawn tool do? +

Request a NEW local coding session from voice/chat (tab spawn). Queues a sticky for the desk launcher on THIS operator's machine (host must run attention-launcher). Use when they say "start a Grok/Claude on …", "new build for …", "open a session for …". Does not open a cloud IDE — the local launcher opens Terminal + announces + optional first directive. [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 Execute tool in the Freedom Mcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does request_attention_spawn accept? +

request_attention_spawn accepts 6 parameters: cwd, goal, host, companyId, session_id, first_instruction. Required: goal, host. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on request_attention_spawn? +

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

request_attention_spawn is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit request_attention_spawn? +

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

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

request_attention_spawn 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 → High-risk tools on this server →

Across the catalogue

spawn on Frida Game Hacking MCP →request_elevation on Procmon → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →