get_product_request_status
Check status of a product request you previously filed with submit_product_request for your operator. Returns pending | approved | denied | dismissed | completed so you can tell your human when FreedomOS product team decides. Use when you hold a request_id and need an update for the filer.
This record as markdown: /tools/com-getfreedomos-freedom-mcp/get-product-request-status.md
What get_product_request_status does on Freedom Mcp
AI agents call get_product_request_status 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 |
|---|---|---|---|
companyId | string | — | FreedomOS company id to act within (you must be a member). Required for company-scoped tools. |
request_id | string | Yes | The request_id UUID returned by submit_product_request |
Parameters from the server's own tool schema.
Why get_product_request_status is rated Low
get_product_request_status is a query operation that retrieves the current status of a previously filed product request. It has no capability to create, modify, delete, or execute anything—it only reads and returns status information. This is a straightforward Read category tool with minimal security risk, justifying low severity.
From the tool's definition Tool description states 'Check status' and 'Returns pending | approved | denied | dismissed | completed' — purely retrieves status information with no side effects or state changes.
Attacks that exploit this kind of access
The rule that runs get_product_request_status 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 get_product_request_status, this is the rule to start with:
get_product_request_status 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 get_product_request_status call is checked against it from then on.
Questions about get_product_request_status
Check status of a product request you previously filed with submit_product_request for your operator. Returns pending | approved | denied | dismissed | completed so you can tell your human when FreedomOS product team decides. Use when you hold a request_id and need an update for the filer. It is categorised as a Read tool in the Freedom Mcp MCP Server, which means it retrieves data without modifying state.
get_product_request_status accepts 2 parameters: companyId, request_id. Required: request_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 get_product_request_status: 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.
get_product_request_status 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 get_product_request_status 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 get_product_request_status. 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.
get_product_request_status 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