query_lead_journey
Reconstruct the full journey of a lead — what they did on the site, what they signaled, what we have already sent them. Returns structured data that downstream synthesis or drafting tools consume. Use this as the first step before synthesizing a hypothesis about why a lead behaved a certain way o...
This record as markdown: /tools/com-getfreedomos-freedom-mcp/query-lead-journey.md
What query_lead_journey does on Freedom Mcp
AI agents call query_lead_journey 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 |
|---|---|---|---|
lead_id | string | Yes | UUID of the lead in the leads table. |
companyId | string | Yes | 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 query_lead_journey is rated Low
This tool retrieves and reconstructs historical lead journey data (site activity, signals, outreach history). It has no side effects, does not modify records, execute operations, or commit financial actions.
From the tool's definition Tool description states it 'Reconstruct the full journey of a lead — what they did on the site, what they signaled, what we have already sent them.
Attacks that exploit this kind of access
The rule that runs query_lead_journey 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 query_lead_journey, this is the rule to start with:
query_lead_journey 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 query_lead_journey call is checked against it from then on.
Questions about query_lead_journey
Reconstruct the full journey of a lead — what they did on the site, what they signaled, what we have already sent them. Returns structured data that downstream synthesis or drafting tools consume. Use this as the first step before synthesizing a hypothesis about why a lead behaved a certain way or drafting outreach to them. It is categorised as a Read tool in the Freedom Mcp MCP Server, which means it retrieves data without modifying state.
query_lead_journey accepts 2 parameters: lead_id, companyId. Required: lead_id, 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 query_lead_journey: 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.
query_lead_journey 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 query_lead_journey 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 query_lead_journey. 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.
query_lead_journey 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