search_near_fungible_tokens
AI agents call search_near_fungible_tokens to retrieve information from NEAR MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name suggests querying/listing fungible tokens on the NEAR blockchain, which is a Read operation. The absence of descriptive text and verbs like 'create', 'delete', 'transfer', or 'execute' supports classification as a read-only query. Confidence is moderate (0.7) due to empty description; if it performs unexpected writes or executions, severity could escalate.
From the tool's definition Tool name 'search_near_fungible_tokens' indicates a search operation. Description is empty, limiting evidence, but 'search' typically retrieves or queries data without side effects.
Documented attack patterns abuse exactly the kind of access search_near_fungible_tokens gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and NEAR MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for search_near_fungible_tokens:
{
"version": "1",
"default": "deny",
"tools": {
"search_near_fungible_tokens": {}
}
}search_near_fungible_tokens 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.
search_near_fungible_tokens. It is categorised as a Read tool in the NEAR MCP MCP Server, which means it retrieves data without modifying state.
Register the NEAR MCP server in PolicyLayer and add a rule for search_near_fungible_tokens: 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 NEAR MCP. Nothing to install.
search_near_fungible_tokens 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 search_near_fungible_tokens 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 search_near_fungible_tokens. 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.
search_near_fungible_tokens is provided by the NEAR MCP server (nearai/near-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from NEAR MCP, 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.
23 NEAR MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.