setCollateral · Kaskad Protocol MCP Server MCP

WHAT IT DOES

What setCollateral does on Kaskad Protocol MCP Server

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

WHY IT NEEDS A POLICY

Why setCollateral needs a policy

This tool modifies collateral settings on a DeFi lending protocol, which directly affects the wallet's borrowing capacity and risk profile. While reversible (Write rather than Destructive), misuse could cause significant financial damage — an agent could disable critical collateral, triggering liquidation, or enable inappropriate assets as collateral, increasing default risk.

From the tool's definition Tool description states 'Enable or disable an asset as collateral' — these are reversible modifications to collateral configuration for the connected wallet. The words 'enable or disable' indicate state changes that can be toggled, not permanent deletion.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

setCollateral Rate-limited

setCollateral 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": {
    "setCollateral": {
      "limits": [
        {
          "counter": "setcollateral_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 Kaskad Protocol MCP Server, so you can run agents against it safely.

FAQ

Questions about setCollateral

What does the setCollateral tool do? +

Enable or disable an asset as collateral for the connected wallet on Kaskad Protocol. It is categorised as a Write tool in the Kaskad Protocol MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on setCollateral? +

Register the Kaskad Protocol MCP Server MCP server in PolicyLayer and add a rule for setCollateral: 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 Kaskad Protocol MCP Server. Nothing to install.

What risk level is setCollateral? +

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

Can I rate-limit setCollateral? +

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

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

setCollateral is provided by the Kaskad Protocol MCP Server MCP server (kaskad-lending/kaskad-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.