Update existing Arkadiko vault by adjusting collateral or debt
AI agents use arkadiko_update_vault to create or update resources in Stacks AI MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Stacks AI MCP Server environment.
This tool modifies an existing DeFi vault's collateral or debt positions on the Stacks blockchain. While it is reversible in principle (positions can be re-adjusted), incorrect adjustments could expose the vault to liquidation risk, making the blast radius high. It falls under Write as it modifies existing data rather than irreversibly deleting it or directly moving money.
From the tool's definition Update existing Arkadiko vault by adjusting collateral or debt
Attacks that exploit this kind of access
Update existing Arkadiko vault by adjusting collateral or debt. It is categorised as a Write tool in the Stacks AI MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Stacks AI MCP Server MCP server in PolicyLayer and add a rule for arkadiko_update_vault: 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 Stacks AI MCP Server. Nothing to install.
arkadiko_update_vault 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 arkadiko_update_vault 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 arkadiko_update_vault. 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.
arkadiko_update_vault is provided by the Stacks AI MCP Server MCP server (stack-ai-mcp/stacks-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 →