meteora_createAlphaVault
Create a Meteora Alpha Vault for fair token launches with vesting. SAP MCP context: This Synapse AgentKit tool is served beside the sap_* SDK tools. Use sap_agent_identity_plan, sap_payments_register_agent, sap_payments_update_agent, and sap_publish_tool_by_name when the capability should become ...
This record as markdown: /tools/oobe-protocol-labs-sap-mcp-server/meteora-createalphavault.md
What meteora_createAlphaVault does on Sap
AI agents use meteora_createAlphaVault to create or update resources in Sap, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sap environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
creator | string | Yes | Solana public key (base58) |
startTime | number | — | Vault start time (Unix timestamp) |
maxDeposit | string | Yes | Maximum deposit cap |
depositMint | string | Yes | Token mint accepted for deposits |
poolAddress | string | Yes | Solana public key (base58) |
vestingDuration | number | Yes | Vesting duration in seconds |
Parameters from the server's own tool schema.
Why meteora_createAlphaVault is rated Medium
Creates and modifies token vault configuration with financial implications and ongoing vesting obligations.
From the tool's definition Create Meteora Alpha Vault for token launches with vesting, paid tool.
Attacks that exploit this kind of access
The rule that runs meteora_createAlphaVault safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sap, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For meteora_createAlphaVault, this is the rule to start with:
meteora_createAlphaVault 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Sap, apply this rule, and every meteora_createAlphaVault call is checked against it from then on.
Questions about meteora_createAlphaVault
Create a Meteora Alpha Vault for fair token launches with vesting. SAP MCP context: This Synapse AgentKit tool is served beside the sap_* SDK tools. Use sap_agent_identity_plan, sap_payments_register_agent, sap_payments_update_agent, and sap_publish_tool_by_name when the capability should become part of an on-chain SAP agent profile or tool registry entry. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: hosted accountless write is blocked; do not call this as a paid hosted write and no x402 payment should be charged. Use the local sap_payments bridge or a hosted unsigned builder when user signing is required. Signer boundary: user-controlled local profile or external signer; OOBE hosted MCP remains non-custodial. It is categorised as a Write tool in the Sap MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
meteora_createAlphaVault accepts 6 parameters: creator, startTime, maxDeposit, depositMint, poolAddress, vestingDuration. Required: creator, maxDeposit, depositMint, poolAddress, vestingDuration. The full parameter table on this page comes from the server's own tool schema.
Register the Sap MCP server in PolicyLayer and add a rule for meteora_createAlphaVault: 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 Sap. Nothing to install.
meteora_createAlphaVault 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 meteora_createAlphaVault 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 meteora_createAlphaVault. 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.
meteora_createAlphaVault is provided by the Sap MCP server (https://mcp.sap.oobeprotocol.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Sap, and thousands of servers like it.
This server
Across the catalogue