Used to look up the transaction signatures associated with a compressed asset. You can identify the asset either by
AI agents call getAssetSignatures to retrieve information from Solana MCP Demo without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical transaction data for a given asset identifier. It performs a lookup/fetch operation with no ability to modify, execute code, delete data, or commit financial transactions. The operation is read-only and safe even if called repeatedly or with unexpected arguments.
From the tool's definition Tool name 'getAssetSignatures' and description indicate it 'look up the transaction signatures associated with a compressed asset' — a pure query operation with no side effects.
Attacks that exploit this kind of access
Used to look up the transaction signatures associated with a compressed asset. You can identify the asset either by. It is categorised as a Read tool in the Solana MCP Demo MCP Server, which means it retrieves data without modifying state.
Register the Solana MCP Demo MCP server in PolicyLayer and add a rule for getAssetSignatures: 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 MCP Demo. Nothing to install.
getAssetSignatures 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 getAssetSignatures 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 getAssetSignatures. 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.
getAssetSignatures is provided by the Solana MCP Demo MCP server (metaplex-foundation/das-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 →