Enable or disable a supplied asset to be used as collateral.
AI agents use set_collateral_status to create or update resources in SEI MCP Server V2 — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SEI MCP Server V2 environment.
This tool modifies blockchain state by changing whether an asset can serve as collateral in a lending/borrowing protocol. While reversible (user can toggle back), it has significant financial implications as collateral status affects borrowing capacity, liquidation risk, and overall portfolio configuration.
From the tool's definition Tool enables modification of collateral status (enable/disable) on a blockchain asset, which changes the financial configuration of a user's position.
Attacks that exploit this kind of access
Enable or disable a supplied asset to be used as collateral. It is categorised as a Write tool in the SEI MCP Server V2 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the SEI MCP Server V2 MCP server in PolicyLayer and add a rule for set_collateral_status: 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 SEI MCP Server V2. Nothing to install.
set_collateral_status 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 set_collateral_status 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 set_collateral_status. 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.
set_collateral_status is provided by the SEI MCP Server V2 MCP server (testinguser1111111/sei-mcp-server). 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 →