wait-seconds

THE RISK

Low Risk

Why wait-seconds needs a policy

This tool introduces a time delay and nothing else. It does not read, write, execute, destroy, or move money. It is a utility timing function with minimal blast radius, though it could theoretically be used to slow down agent operations.

From the tool's definition 'Wait the given seconds' — purely a timing/delay operation with no data access, modification, or execution side effects

Documented attack patterns abuse exactly the kind of access wait-seconds gives an agent:

POLICY

How to control wait-seconds

PolicyLayer is an MCP gateway — it sits between your AI agents and MetaMask MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for wait-seconds:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "wait-seconds": {
      "limits": [
        {
          "counter": "wait-seconds_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

wait-seconds gets a rate cap, and everything else on the server is denied unless you say otherwise.

Create a free account and register MetaMask MCP — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

SET A RULE FOR THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More MetaMask MCP tools

Financial send-transaction Send transactions to networks. Execute deploy-contract Deploy a contract to the network, given bytecode, and constructor arguments. Execute call Executing a new message call immediately without submitting a transaction to the network. Execute sign-message Sign a message. Execute switch-chain Switch the target chain. Execute write-contract Execute a write function on a contract. Write disconnect Disconnect the wallet. Read wait-for-transaction-receipt Waits for the transaction to be included on a block, and then returns the transaction rece

All 29 MetaMask MCP tools →

Other tools on other servers

Android Forensics ADB MCP Server generate_app_analysis_report Ethereum Tools add Math MCP Server complex_analysis_suite Crypto_MCP aes_encrypt

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Tool risk categories → How PolicyLayer classifies MCP tools by what they can do.
MCP tool → What an MCP tool is and how clients discover and call it.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about wait-seconds

What does the wait-seconds tool do? +

Wait the given seconds. It is categorised as a Other tool in the MetaMask MCP MCP Server, which means it performs auxiliary operations.

How do I enforce a policy on wait-seconds? +

Register the MetaMask MCP server in PolicyLayer and add a rule for wait-seconds: 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 MetaMask MCP. Nothing to install.

What risk level is wait-seconds? +

wait-seconds is a Other tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit wait-seconds? +

Yes. Add a rate_limit block to the wait-seconds 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.

How do I block wait-seconds completely? +

Set action: deny in the PolicyLayer policy for wait-seconds. 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 wait-seconds? +

wait-seconds is provided by the MetaMask MCP server (xiawpohr/metamask-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MetaMask MCP tool call.

Start from MetaMask MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →