AI agents call search_fungibles to retrieve information from Zerion without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a query-only operation to retrieve token information. It does not create, modify, delete, or execute any external operations. The search functionality is purely informational and read-only, consistent with other Read-category tools on this server like get_fungible_by_id and get_chains. Confidence is high due to explicit 'search' and 'filter' language indicating data retrieval without side effects.
From the tool's definition Tool description states 'Search for fungible assets (tokens) by name/symbol or filter by implementation' — a search/filter operation with no mutation or side effects.
Attacks that exploit this kind of access
Search for fungible assets (tokens) by name/symbol or filter by implementation. It is categorised as a Read tool in the Zerion MCP Server, which means it retrieves data without modifying state.
Register the Zerion MCP server in PolicyLayer and add a rule for search_fungibles: 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 Zerion. Nothing to install.
search_fungibles 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_fungibles 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_fungibles. 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_fungibles is provided by the Zerion MCP server (rockyale/zerion-mcp). 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 →