Execute Blaze intent for subnet operations
AI agents invoke charisma_execute_intent to trigger actions in Stacks AI MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool runs code/operations on a blockchain network ('subnet operations'), making it Execute rather than Write. The use of 'intent' and 'subnet operations' suggests complex state-modifying actions that depend on user-supplied parameters.
From the tool's definition Tool name contains 'execute' and description states 'Execute Blaze intent for subnet operations' — indicates execution of arbitrary blockchain operations on the Stacks Layer 2 network whose effects depend on the intent arguments provided.
Attacks that exploit this kind of access
Execute Blaze intent for subnet operations. It is categorised as a Execute tool in the Stacks AI MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Stacks AI MCP Server MCP server in PolicyLayer and add a rule for charisma_execute_intent: 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.
charisma_execute_intent is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the charisma_execute_intent 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 charisma_execute_intent. 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.
charisma_execute_intent 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 →