lithtrix_feedback · Lithtrix MCP: Risk & Policy

WHAT IT DOES

What lithtrix_feedback does on Lithtrix

AI agents use lithtrix_feedback to create or update resources in Lithtrix — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Lithtrix environment.

WHY IT NEEDS A POLICY

Why lithtrix_feedback needs a policy

This tool creates or modifies feedback records in the persistent memory system. It is a reversible write operation—feedback can be updated or cleared. The blast radius is low because feedback signals do not directly alter search results, delete data, execute code, or move funds. Misuse would only result in corrupted feedback metadata, not system compromise or data loss.

From the tool's definition Tool enables recording feedback signals (helpful/unhelpful/wrong) against search results, which modifies persistent memory state. Description states 'send...signal' indicating data modification. Uses 'ref_type search_id' parameters to target specific records.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

lithtrix_feedback Rate-limited

lithtrix_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "lithtrix_feedback": {
      "limits": [
        {
          "counter": "lithtrix_feedback_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Lithtrix, so you can run agents against it safely.

FAQ

Questions about lithtrix_feedback

What does the lithtrix_feedback tool do? +

After lithtrix_search, send helpful / unhelpful / wrong signal using ref_type search_id and. It is categorised as a Write tool in the Lithtrix MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on lithtrix_feedback? +

Register the Lithtrix MCP server in PolicyLayer and add a rule for lithtrix_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 Lithtrix. Nothing to install.

What risk level is lithtrix_feedback? +

lithtrix_feedback is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit lithtrix_feedback? +

Yes. Add a rate_limit block to the lithtrix_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.

How do I block lithtrix_feedback completely? +

Set action: deny in the PolicyLayer policy for lithtrix_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.

What MCP server provides lithtrix_feedback? +

lithtrix_feedback is provided by the Lithtrix MCP server (lithtrix/lithtrix-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.