list_inbox
List pending ideas in the user's Ideas. Shows ideas that haven't been triaged yet.
This record as markdown: /tools/com-getfreedomos-freedom-mcp/list-inbox.md
What list_inbox does on Freedom Mcp
AI agents call list_inbox 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 | — | Maximum number of ideas to return (default: 10) |
status | string | — | Filter by status: new (default), parked, or all pending ideas |
companyId | string | — | FreedomOS company id to act within (you must be a member). Required for company-scoped tools. |
Parameters from the server's own tool schema.
Why list_inbox is rated Low
This tool performs a straightforward query operation to retrieve and display a list of untriaged ideas from the user's inbox. It has no side effects, does not modify data, and does not execute external operations. The blast radius of misuse is minimal—an agent could only retrieve information the user already has access to.
From the tool's definition Tool name 'list_inbox' and description 'List pending ideas' and 'Shows ideas that haven't been triaged yet' indicate a read-only operation that retrieves and displays data without modification.
Attacks that exploit this kind of access
The rule that runs list_inbox 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_inbox, this is the rule to start with:
list_inbox 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_inbox call is checked against it from then on.
Questions about list_inbox
List pending ideas in the user's Ideas. Shows ideas that haven't been triaged yet. It is categorised as a Read tool in the Freedom Mcp MCP Server, which means it retrieves data without modifying state.
list_inbox accepts 3 parameters: limit, status, companyId. 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_inbox: 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_inbox 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_inbox 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_inbox. 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_inbox 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