stocktoken_execute_plan
Build non-custodial tx plan (approve + swap) via best venue (Uniswap / 0x). Does NOT sign or broadcast. Chain 4663.
This record as markdown: /tools/dev-aatos-aatos/stocktoken-execute-plan.md
What stocktoken_execute_plan does on AI Agent Tokenized Stock OS
AI agents invoke stocktoken_execute_plan to trigger actions in AI Agent Tokenized Stock OS. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
owner | string | Yes | |
tokenIn | string | Yes | |
amountIn | string | — | |
tokenOut | string | Yes | |
sessionId | string | — | |
approveMax | boolean | — | |
notionalUsd | number | — | |
slippageBps | integer | — | |
amountInHuman | string | — |
Parameters from the server's own tool schema.
Why stocktoken_execute_plan is rated High
stocktoken_execute_plan triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Attacks that exploit this kind of access
The rule that runs stocktoken_execute_plan safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AI Agent Tokenized Stock OS, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For stocktoken_execute_plan, this is the rule to start with:
stocktoken_execute_plan stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect AI Agent Tokenized Stock OS, apply this rule, and every stocktoken_execute_plan call is checked against it from then on.
Questions about stocktoken_execute_plan
Build non-custodial tx plan (approve + swap) via best venue (Uniswap / 0x). Does NOT sign or broadcast. Chain 4663. It is categorised as a Execute tool in the AI Agent Tokenized Stock OS MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
stocktoken_execute_plan accepts 9 parameters: owner, tokenIn, amountIn, tokenOut, sessionId, approveMax, notionalUsd, slippageBps, amountInHuman. Required: owner, tokenIn, tokenOut. The full parameter table on this page comes from the server's own tool schema.
Register the AI Agent Tokenized Stock OS MCP server in PolicyLayer and add a rule for stocktoken_execute_plan: 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 AI Agent Tokenized Stock OS. Nothing to install.
stocktoken_execute_plan 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 stocktoken_execute_plan 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 stocktoken_execute_plan. 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.
stocktoken_execute_plan is provided by the AI Agent Tokenized Stock OS MCP server (https://aatos.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on AI Agent Tokenized Stock OS, and thousands of servers like it.
Across the catalogue