Medium Risk

approve_token_spending

Approve ERC20 spender (for DEX/lending). DRY_RUN default — pass confirm='CONFIRMED'. Use infinite=true for max approval.

Part of the Kosyak Evm MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

kosyak-evm-mcp-server Write Risk 2/5

AI agents use approve_token_spending to create or modify resources in Kosyak Evm. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call approve_token_spending repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Kosyak Evm.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

kosyak-evm.yaml
tools:
  approve_token_spending:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Kosyak Evm policy for all 43 tools.

Tool Name approve_token_spending
Category Write
Risk Level Medium

View all 43 tools →

Agents calling write-class tools like approve_token_spending have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

What does the approve_token_spending tool do? +

Approve ERC20 spender (for DEX/lending). DRY_RUN default — pass confirm='CONFIRMED'. Use infinite=true for max approval.. It is categorised as a Write tool in the Kosyak Evm MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on approve_token_spending? +

Add a rule in your Intercept YAML policy under the tools section for approve_token_spending. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Kosyak Evm MCP server.

What risk level is approve_token_spending? +

approve_token_spending is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit approve_token_spending? +

Yes. Add a rate_limit block to the approve_token_spending rule in your Intercept 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.

How do I block approve_token_spending completely? +

Set action: deny in the Intercept policy for approve_token_spending. 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.

What MCP server provides approve_token_spending? +

approve_token_spending is provided by the Kosyak Evm MCP server (kosyak-evm-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Kosyak Evm

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.