report_feedback
Report an error, issue, observation, or suggestion you encountered during your work. Use this proactively when you notice something noteworthy — tool failures, recurring problems, quality issues, or improvement ideas. This helps the founder track and act on agent insights over time. Routing: For ...
This record as markdown: /tools/com-getfreedomos-freedom-mcp/report-feedback.md
What report_feedback does on Freedom Mcp
AI agents use report_feedback to create or update resources in Freedom Mcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Freedom Mcp environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
title | string | Yes | Short summary of the issue (1 line). Be specific — "Buffer API returns 429 on image posts" not "API error". |
category | string | Yes | Type of feedback. error = something broke. warning = something might break. observation = pattern noticed. suggestion = improvement idea. blocker = cannot compl |
severity | string | — | How urgent this is. Default: medium. Use critical only for data loss or security issues. |
companyId | string | Yes | FreedomOS company id to act within (you must be a member). Required for company-scoped tools. |
tool_name | string | — | The tool that was involved, if applicable (e.g., "generate_image_xai", "post_to_x"). |
description | string | Yes | Detailed explanation. Include: what happened, what you expected, what you tried, and any error messages or codes. |
context_json | string | — | Optional JSON-encoded structured context (error codes, retry counts, URLs, timestamps, etc.). Example: "{\"status\":429,\"retries\":3}". |
Parameters from the server's own tool schema.
Why report_feedback is rated Medium
This tool writes feedback data to a log or database (observability feed) but does not execute external operations, delete data, move money, or trigger side effects beyond record creation. It is reversible (feedback can be deleted or modified). The blast radius of misuse is minimal—an AI could spam feedback, but this would not cause financial loss, data destruction, or system compromise.
From the tool's definition Tool creates feedback records ('Report an error, issue, observation, or suggestion') that are stored in observability feeds.
Attacks that exploit this kind of access
The rule that runs report_feedback 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 report_feedback, this is the rule to start with:
report_feedback stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 report_feedback call is checked against it from then on.
Questions about report_feedback
Report an error, issue, observation, or suggestion you encountered during your work. Use this proactively when you notice something noteworthy — tool failures, recurring problems, quality issues, or improvement ideas. This helps the founder track and act on agent insights over time. Routing: For issues YOU observe doing tenant work (tool failures, quality patterns) — lands in the operator's own observability feed. If the operator is reporting that FreedomOS ITSELF (platform UI/MCP/runtime) is broken or missing a capability, route to submit_product_request instead — FO product inbox only. Do NOT use submit_product_request for the tenant's own app/product/KB/retrieval gaps. [write-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 Write tool in the Freedom Mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
report_feedback accepts 7 parameters: title, category, severity, companyId, tool_name, description, context_json. Required: title, category, companyId, description. 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 report_feedback: 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.
report_feedback is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the report_feedback 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 report_feedback. 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.
report_feedback 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