Make an HTTP request to NFTGo API(${host}) based on the OpenAPI specifications returned by the api-path-schema tool.
AI agents call request to retrieve information from NFTGo MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool is classified as Read because it retrieves data from the NFTGo API (collection details, assets, market data, wallet information) without modifying or deleting data. The HTTP request mechanism itself is neutral, but the context—querying an NFT blockchain data API—indicates queries and data retrieval operations. No write, delete, financial movement, or code execution capabilities are described.
From the tool's definition Tool makes HTTP requests to retrieve NFT collection details, asset information, market data, and wallet information from NFTGo API. Description indicates data retrieval with no modification or destructive capabilities mentioned.
Attacks that exploit this kind of access
Make an HTTP request to NFTGo API(${host}) based on the OpenAPI specifications returned by the api-path-schema tool. It is categorised as a Read tool in the NFTGo MCP Server MCP Server, which means it retrieves data without modifying state.
Register the NFTGo MCP Server MCP server in PolicyLayer and add a rule for request: 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 NFTGo MCP Server. Nothing to install.
request 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 request 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 request. 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.
request is provided by the NFTGo MCP Server MCP server (nftgo/mcp-nftgo-api). 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 →