get_daily_active_addresses
AI agents call get_daily_active_addresses to retrieve information from Solana Launchpads without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries activity metrics—specifically daily active addresses across Solana launchpads—with no apparent side effects, modification, or deletion capability. It fits the 'Read' category as a fetch/query operation. Severity is low because misuse would only expose historical or current state data without enabling destructive or financial harm.
From the tool's definition Tool name 'get_daily_active_addresses' and server context indicate data retrieval of Solana launchpad metrics without any modification capability.
Attacks that exploit this kind of access
get_daily_active_addresses. It is categorised as a Read tool in the Solana Launchpads MCP Server, which means it retrieves data without modifying state.
Register the Solana Launchpads MCP server in PolicyLayer and add a rule for get_daily_active_addresses: 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 Solana Launchpads. Nothing to install.
get_daily_active_addresses 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 get_daily_active_addresses 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_daily_active_addresses. 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_daily_active_addresses is provided by the Solana Launchpads MCP server (kukapay/solana-launchpads-mcp). 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 →