lithtrix_reputation_dispute · Lithtrix MCP: Risk & Policy

WHAT IT DOES

What lithtrix_reputation_dispute does on Lithtrix

AI agents use lithtrix_reputation_dispute 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_reputation_dispute needs a policy

This tool sends a POST request to dispute a reputation event, which creates/modifies data (a dispute record) in the system. It is reversible in the sense that submitting a dispute doesn't permanently destroy data — it adds a dispute entry. The blast radius is medium because misuse could spam disputes (rate-limited to 3/UTC day) or manipulate reputation records, but it doesn't delete data or move money.

From the tool's definition POST /v1/reputation/dispute — dispute a reputation event where you are the subject

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

lithtrix_reputation_dispute Rate-limited

lithtrix_reputation_dispute 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_reputation_dispute": {
      "limits": [
        {
          "counter": "lithtrix_reputation_dispute_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_reputation_dispute

What does the lithtrix_reputation_dispute tool do? +

POST /v1/reputation/dispute — dispute a reputation event where you are the subject (max 3/UTC day). 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_reputation_dispute? +

Register the Lithtrix MCP server in PolicyLayer and add a rule for lithtrix_reputation_dispute: 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_reputation_dispute? +

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

Can I rate-limit lithtrix_reputation_dispute? +

Yes. Add a rate_limit block to the lithtrix_reputation_dispute 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_reputation_dispute completely? +

Set action: deny in the PolicyLayer policy for lithtrix_reputation_dispute. 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_reputation_dispute? +

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