Complete governance workflow: Stake DIKO, create proposal, and vote
AI agents use arkadiko_complete_governance_workflow to commit financial operations through Stacks AI MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool performs multiple high-impact DeFi operations in sequence: staking tokens (commits financial assets), creating governance proposals (on-chain write operation with potential protocol-level consequences), and voting (executes binding governance decisions).
From the tool's definition Complete governance workflow: Stake DIKO, create proposal, and vote
Attacks that exploit this kind of access
Complete governance workflow: Stake DIKO, create proposal, and vote. It is categorised as a Financial tool in the Stacks AI MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Stacks AI MCP Server MCP server in PolicyLayer and add a rule for arkadiko_complete_governance_workflow: 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_complete_governance_workflow is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the arkadiko_complete_governance_workflow 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_complete_governance_workflow. 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_complete_governance_workflow 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 →