AI agents use send_erc20_token to create or update resources in EDUCHAIN Agent Kit — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your EDUCHAIN Agent Kit environment.
This tool transfers ERC20 tokens between wallet addresses. While superficially a 'Write' operation (modifies data), it involves movement of financial assets. However, since it transfers existing tokens rather than creating financial obligations, committing new contracts, or charging fees/debts, it is Write rather than Financial.
From the tool's definition "Send ERC20 token to another wallet address" — transfers cryptocurrency assets to external addresses, which modifies blockchain state and account balances irreversibly.
Documented attack patterns abuse exactly the kind of access send_erc20_token gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and EDUCHAIN Agent Kit, and nothing reaches the server without passing your rules. This is the rule we recommend for send_erc20_token:
{
"version": "1",
"default": "deny",
"tools": {
"send_erc20_token": {
"limits": [
{
"counter": "send_erc20_token_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} send_erc20_token stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Send ERC20 token to another wallet address. It is categorised as a Write tool in the EDUCHAIN Agent Kit MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the EDUCHAIN Agent Kit MCP server in PolicyLayer and add a rule for send_erc20_token: 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 EDUCHAIN Agent Kit. Nothing to install.
send_erc20_token is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the send_erc20_token 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 send_erc20_token. 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.
send_erc20_token is provided by the EDUCHAIN Agent Kit MCP server (sailfish-finance/educhain-ai-agent-kit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from EDUCHAIN Agent Kit, 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.
29 EDUCHAIN Agent Kit tools catalogued and risk-classified — across an index of 43,000+ MCP servers.