velar_get_pool_by_lp_token
Get pool information by LP token address
This record as markdown: /tools/stack-ai-mcp-stacks-mcp-server/velar-get-pool-by-lp-token.md
What velar_get_pool_by_lp_token does on Stacks AI MCP Server
AI agents call velar_get_pool_by_lp_token to retrieve information from Stacks AI MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why velar_get_pool_by_lp_token is rated Low
This is a straightforward read operation that queries and returns pool information. It does not create, modify, delete, or execute any operations - it only retrieves existing data. The tool has minimal blast radius if misused by an AI agent, as it cannot cause financial transactions, state changes, or data loss.
From the tool's definition Tool name contains 'get' and description states 'Get pool information' - a retrieval operation with no side effects. Returns data about an existing pool using an LP token address as a lookup parameter.
Attacks that exploit this kind of access
The rule that runs velar_get_pool_by_lp_token safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Stacks AI MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For velar_get_pool_by_lp_token, this is the rule to start with:
velar_get_pool_by_lp_token is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Stacks AI MCP Server, apply this rule, and every velar_get_pool_by_lp_token call is checked against it from then on.
Questions about velar_get_pool_by_lp_token
Get pool information by LP token address. It is categorised as a Read tool in the Stacks AI MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Stacks AI MCP Server MCP server in PolicyLayer and add a rule for velar_get_pool_by_lp_token: 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.
velar_get_pool_by_lp_token is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the velar_get_pool_by_lp_token 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 velar_get_pool_by_lp_token. 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.
velar_get_pool_by_lp_token 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.
More on Stacks AI MCP Server, and thousands of servers like it.
This server
Across the catalogue