list_attention_directives
List pending attention directives for THIS operator (optionally filtered by target_session_id). Hosts (Grok/Claude) and CoS use this to see what is waiting. Does not ack — use ack_attention_directive after acting.
This record as markdown: /tools/com-getfreedomos-freedom-mcp/list-attention-directives.md
What list_attention_directives does on Freedom Mcp
AI agents call list_attention_directives to retrieve information from Freedom Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | number | — | Max rows (1–50, default 20). |
companyId | string | — | FreedomOS company id to act within (you must be a member). Required for company-scoped tools. |
target_session_id | string | — | If set, only pending directives for this session id. |
Parameters from the server's own tool schema.
Why list_attention_directives is rated Low
This tool retrieves and queries data (attention directives) filtered by optional parameters, with no capacity to modify, delete, or execute actions. The description explicitly clarifies it is passive read-only and that separate tools (ack_attention_directive) handle state changes. Blast radius if misused is negligible: an agent listing directives cannot harm systems or data.
From the tool's definition Tool name is 'list_*' and description states it 'List[s] pending attention directives' with explicit mention that it 'Does not ack' — a read-only query operation. No side effects, creation, modification, deletion, or execution mentioned.
Attacks that exploit this kind of access
The rule that runs list_attention_directives 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 list_attention_directives, this is the rule to start with:
list_attention_directives is read-only, so it stays allowed. 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 list_attention_directives call is checked against it from then on.
Questions about list_attention_directives
List pending attention directives for THIS operator (optionally filtered by target_session_id). Hosts (Grok/Claude) and CoS use this to see what is waiting. Does not ack — use ack_attention_directive after acting. It is categorised as a Read tool in the Freedom Mcp MCP Server, which means it retrieves data without modifying state.
list_attention_directives accepts 3 parameters: limit, companyId, target_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 list_attention_directives: 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.
list_attention_directives is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_attention_directives 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 list_attention_directives. 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.
list_attention_directives 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