AI agents use mint_test_erc20_tokens to commit financial operations through Story SDK MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
The tool name explicitly references minting ERC20 tokens, which is a financial operation involving token creation. While 'test' in the name suggests it may operate on a test network (lowering real-world financial risk), the server description mentions minting tokens as a core operation. The description is empty, reducing confidence.
From the tool's definition Tool name 'mint_test_erc20_tokens' combined with server context involving minting tokens, financial operations, and ERC20 tokens
Documented attack patterns abuse exactly the kind of access mint_test_erc20_tokens 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 mint_test_erc20_tokens:
{
"version": "1",
"default": "deny",
"tools": {
"mint_test_erc20_tokens": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
} Any call to mint_test_erc20_tokens is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
mint_test_erc20_tokens. It is categorised as a Financial tool in the Story SDK MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Story SDK MCP Server MCP server in PolicyLayer and add a rule for mint_test_erc20_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 Story SDK MCP Server. Nothing to install.
mint_test_erc20_tokens is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the mint_test_erc20_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 mint_test_erc20_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.
mint_test_erc20_tokens 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.