check_my_inbox
Check your own agent email inbox (receive-only) for messages sent to your @agents.getfreedomos.com address, and read them. Returns recent unread messages: sender, subject, a safe text snippet, any OTP codes, and login links that are safe to open — reads only YOUR mailbox. Use when a login, sign-i...
This record as markdown: /tools/com-getfreedomos-freedom-mcp/check-my-inbox.md
What check_my_inbox does on Freedom Mcp
AI agents call check_my_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 | — | Max messages to return (default 10, cap 25). |
companyId | string | Yes | FreedomOS company id to act within (you must be a member). Required for company-scoped tools. |
from_domain | string | — | Only return mail whose sender is at this domain (e.g. "getfreedomos.com"). |
since_minutes | number | — | Only return mail received within the last N minutes (e.g. 15 for a fresh login code). |
Parameters from the server's own tool schema.
Why check_my_inbox is rated Low
This is a straightforward data retrieval operation limited to the user's own email inbox. It has no side effects—it only reads messages without creating, modifying, deleting, or executing anything. The sensitivity tier reflects appropriate access controls for authentication flows, but the tool's function remains purely informational.
From the tool's definition Tool description explicitly states it is 'receive-only' and performs 'read' operations: 'Check your own agent email inbox...and read them.' It retrieves 'recent unread messages: sender, subject, a safe text snippet, any OTP codes, and login links' with no…
Attacks that exploit this kind of access
The rule that runs check_my_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 check_my_inbox, this is the rule to start with:
check_my_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 check_my_inbox call is checked against it from then on.
Questions about check_my_inbox
Check your own agent email inbox (receive-only) for messages sent to your @agents.getfreedomos.com address, and read them. Returns recent unread messages: sender, subject, a safe text snippet, any OTP codes, and login links that are safe to open — reads only YOUR mailbox. Use when a login, sign-in, or verification flow tells you it emailed a one-time code or magic link to your agent address and you need to retrieve it. [sensitive-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 Read tool in the Freedom Mcp MCP Server, which means it retrieves data without modifying state.
check_my_inbox accepts 4 parameters: limit, companyId, from_domain, since_minutes. Required: 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 check_my_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.
check_my_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 check_my_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 check_my_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.
check_my_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