get_or_create_pool
Get existing pool or create new DragonSwap V3 pool
This record as markdown: /tools/testinguser1111111-sei-mcp-server/get-or-create-pool.md
What get_or_create_pool does on SEI MCP Server V2
AI agents use get_or_create_pool to create or update resources in SEI MCP Server V2, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SEI MCP Server V2 environment.
Why get_or_create_pool is rated Medium
The tool has dual behavior: if the pool exists, it is a read operation; if it does not exist, it creates a new on-chain pool (a Write action with real blockchain side effects). Since the most severe applicable category must be chosen, this is classified as Write. Creating a new pool on a DEX is a significant on-chain transaction that could lock funds or establish market parameters, warranting high severity.
From the tool's definition 'Get existing pool or create new DragonSwap V3 pool' — the tool may create a new liquidity pool on-chain
Attacks that exploit this kind of access
The rule that runs get_or_create_pool safely
PolicyLayer is an MCP gateway: it sits between your AI agents and SEI MCP Server V2, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_or_create_pool, this is the rule to start with:
get_or_create_pool 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 SEI MCP Server V2, apply this rule, and every get_or_create_pool call is checked against it from then on.
Questions about get_or_create_pool
Get existing pool or create new DragonSwap V3 pool. It is categorised as a Write tool in the SEI MCP Server V2 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the SEI MCP Server V2 MCP server in PolicyLayer and add a rule for get_or_create_pool: 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 SEI MCP Server V2. Nothing to install.
get_or_create_pool 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 get_or_create_pool 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 get_or_create_pool. 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.
get_or_create_pool is provided by the SEI MCP Server V2 MCP server (testinguser1111111/sei-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on SEI MCP Server V2, and thousands of servers like it.
This server
Across the catalogue