Get DAS API compliant NFTs owned by a specific address
AI agents call getAssetsByOwner to retrieve information from AMOCA Solana MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves NFT data associated with a Solana address. It performs a read-only operation on blockchain state without creating, modifying, deleting, or executing any transactions. The blast radius of misuse is limited to unauthorized visibility of an address's NFT holdings, which is typically public blockchain data.
From the tool's definition Tool name 'getAssetsByOwner' and description 'Get DAS API compliant NFTs owned by a specific address' indicate data retrieval with no modification or execution of operations.
Attacks that exploit this kind of access
Get DAS API compliant NFTs owned by a specific address. It is categorised as a Read tool in the AMOCA Solana MCP Server MCP Server, which means it retrieves data without modifying state.
Register the AMOCA Solana MCP Server MCP server in PolicyLayer and add a rule for getAssetsByOwner: 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 AMOCA Solana MCP Server. Nothing to install.
getAssetsByOwner 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 getAssetsByOwner 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 getAssetsByOwner. 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.
getAssetsByOwner is provided by the AMOCA Solana MCP Server MCP server (manolaz/amoca-solana-mcp-server). 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 →