AI agents use lithtrix_passport_sponsor 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.
This tool creates a sponsorship/vouching relationship between two agents via a POST request. It modifies state by establishing a trust relationship (sponsoring a ward), which is reversible (there is a sibling revoke tool: lithtrix_agent_vouch_revoke). Since it writes/creates a relationship record rather than deleting or executing code, Write is the appropriate category.
From the tool's definition POST /v1/agents/{sponsor_id}/sponsor/{ward_id} — vouch for ward (Bearer must match sponsor_id)
Attacks that exploit this kind of access
POST /v1/agents/{sponsor_id}/sponsor/{ward_id} — vouch for ward (Bearer must match sponsor_id). 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.
Register the Lithtrix MCP server in PolicyLayer and add a rule for lithtrix_passport_sponsor: 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.
lithtrix_passport_sponsor 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 lithtrix_passport_sponsor 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 lithtrix_passport_sponsor. 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.
lithtrix_passport_sponsor 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →