upsert_attention_session
Emit or update thin session telemetry for THIS operator (host coding agent self-announce). Use when YOU are Grok or Claude Code at session start / status change so voice CoS can list_attention_sessions and target you. Prefer tiny goals; never dump transcripts. [write-tier — first use may require ...
This record as markdown: /tools/com-getfreedomos-freedom-mcp/upsert-attention-session.md
What upsert_attention_session does on Freedom Mcp
AI agents use upsert_attention_session 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 |
|---|---|---|---|
cwd | string | — | Optional working directory |
goal | string | — | One-line goal |
host | string | — | claude-code | claude-desktop | grok | manual | slack | github | freedomos | other |
status | string | — | running | blocked_on_operator | done | parked | unknown (blocked_on_tim accepted as alias) |
project | string | — | Optional project name |
priority | number | — | Optional priority (higher = sooner) |
companyId | string | — | FreedomOS company id to act within (you must be a member). Required for company-scoped tools. |
company_id | string | — | Optional company id |
session_id | string | Yes | Stable session id (same string used as target_session_id for directives). |
ask_for_operator | string | — | If blocked: one sentence the operator must answer |
Parameters from the server's own tool schema.
Why upsert_attention_session is rated Medium
This tool creates or updates session telemetry records for the current operator (self-announcement). The description emphasizes it emits/updates data (Write behavior), and the write-tier permission model confirms it modifies state.
From the tool's definition Tool description explicitly states 'Emit or update thin session telemetry' and 'write-tier — first use may require a manager's approval', indicating reversible creation/modification of session data.
Risk signalsAccepts file system path (cwd) · Accepts URL/endpoint input (host) · High parameter count (10 properties)
Attacks that exploit this kind of access
The rule that runs upsert_attention_session 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 upsert_attention_session, this is the rule to start with:
upsert_attention_session 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 upsert_attention_session call is checked against it from then on.
Questions about upsert_attention_session
Emit or update thin session telemetry for THIS operator (host coding agent self-announce). Use when YOU are Grok or Claude Code at session start / status change so voice CoS can list_attention_sessions and target you. Prefer tiny goals; never dump transcripts. [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.
upsert_attention_session accepts 10 parameters: cwd, goal, host, status, project, priority, companyId, company_id, session_id, ask_for_operator. Required: session_id. 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 upsert_attention_session: 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.
upsert_attention_session 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 upsert_attention_session 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 upsert_attention_session. 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.
upsert_attention_session 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