lithtrix_passport_set_description

WHAT IT DOES

What lithtrix_passport_set_description does on Lithtrix

AI agents use lithtrix_passport_set_description 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_passport_set_description needs a policy

This is a Write operation: it modifies agent profile data reversibly (description, bio, skills visibility settings can be updated again or reverted). It does not delete data (Destructive), execute arbitrary code (Execute), move money (Financial), or perform side-effect-free queries (Read).

From the tool's definition Tool performs POST request to update agent passport description fields including 'bio', 'skills', 'listed', and 'reputation_sub_signal_visibility' — creating or modifying persistent metadata about an agent's profile.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

lithtrix_passport_set_description Rate-limited

lithtrix_passport_set_description 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_passport_set_description": {
      "limits": [
        {
          "counter": "lithtrix_passport_set_description_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_passport_set_description

What does the lithtrix_passport_set_description tool do? +

POST /v1/agents/passport/description — update bio, skills, listed, and/or reputation_sub_signal_visibility. 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_passport_set_description? +

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

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

Can I rate-limit lithtrix_passport_set_description? +

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

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

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