AI agents call get_nft_metadata to retrieve information from Waiaas without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The verb 'get' combined with 'nft_metadata' strongly indicates a read-only query operation. Metadata retrieval does not modify, delete, execute code, or commit financial transactions. While the description is empty (lowering confidence slightly), the tool name itself provides sufficient evidence for classification as a Read operation.
From the tool's definition Tool name 'get_nft_metadata' indicates retrieval of NFT metadata. No description provided, but the naming pattern and context of a wallet MCP server suggest this is a query operation that retrieves immutable blockchain data about NFTs without modifying state.
Documented attack patterns abuse exactly the kind of access get_nft_metadata gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Waiaas, and nothing reaches the server without passing your rules. This is the rule we recommend for get_nft_metadata:
{
"version": "1",
"default": "deny",
"tools": {
"get_nft_metadata": {}
}
}get_nft_metadata is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
get_nft_metadata. It is categorised as a Read tool in the Waiaas MCP Server, which means it retrieves data without modifying state.
Register the Waiaas MCP server in PolicyLayer and add a rule for get_nft_metadata: 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 Waiaas. Nothing to install.
get_nft_metadata 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_nft_metadata 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_nft_metadata. 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_nft_metadata is provided by the Waiaas MCP server (minhoyoo-iotrust/waiaas). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Waiaas, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
126 Waiaas tools catalogued and risk-classified — across an index of 43,000+ MCP servers.