Get all ERC-20 token holdings for an address, including detailed token information
AI agents call get_token_holdings to retrieve information from Story SDK MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a passive data retrieval operation (read-only query) to fetch wallet holdings and token metadata. While it accesses financial account information, it does not move money, create obligations, or execute trades—it only reads existing blockchain state. The most severe baseline impact is information disclosure, which is typical Read category risk.
From the tool's definition Tool retrieves ERC-20 token holdings and token information for an address without modifying any data. Description explicitly states 'Get' (query operation) with no modification, deletion, or execution of external operations mentioned.
Documented attack patterns abuse exactly the kind of access get_token_holdings gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Story SDK MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_token_holdings:
{
"version": "1",
"default": "deny",
"tools": {
"get_token_holdings": {}
}
}get_token_holdings 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 all ERC-20 token holdings for an address, including detailed token information. It is categorised as a Read tool in the Story SDK MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Story SDK MCP Server MCP server in PolicyLayer and add a rule for get_token_holdings: 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 Story SDK MCP Server. Nothing to install.
get_token_holdings 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_token_holdings 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_token_holdings. 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_token_holdings is provided by the Story SDK MCP Server MCP server (piplabs/story-mcp-hub). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Story SDK MCP Server, 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.
25 Story SDK MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.