PortalMCP

17 tools. 13 can modify or destroy data without limits.

4 destructive tools with no built-in limits. Policy required.

Last updated:

13 can modify or destroy data
4 read-only
17 tools total

Community server · catalogue entry verified 01/07/2026

How to control PortalMCP ↓

What PortalMCP exposes to your agents

Read (4) Write / Execute (9) Destructive / Financial (4)
Critical Risk

The most dangerous PortalMCP tools

13 of PortalMCP's 17 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

How to control PortalMCP

PolicyLayer is an MCP gateway — it sits between your AI agents and PortalMCP, and nothing reaches the server without passing your rules. These are the rules we recommend:

Block financial tools by default
{
  "eth_stake_tokens": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Requires human approval."
      }
    ]
  }
}

Financial tools should be explicitly enabled per use case, not open by default.

Rate limit write operations
{
  "eth_create_nft_collection": {
    "limits": [
      {
        "counter": "eth_create_nft_collection_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
{
  "eth_call_contract": {
    "limits": [
      {
        "counter": "eth_call_contract_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

  1. Create a free account and register PortalMCP — nothing to install.
  2. Add these rules — paste them, or build them visually. Tune the limits to your setup.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
ENFORCE POLICY ON PORTALMCP →

Instant setup, no code required.

All 17 PortalMCP tools

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

Questions about PortalMCP

Can an AI agent move money through the Portal MCP server? +

Yes. The PortalMCP server exposes 4 financial tools including eth_stake_tokens, eth_swap_eth_to_usdt, eth_swap_tokens. Without a policy, an autonomous agent can call these with no spend caps, no rate limits, and no approval flow. PolicyLayer lets you block financial tools by default, require human approval, or set per-tool rate limits — enforced on every call.

How do I prevent bulk modifications through PortalMCP? +

The PortalMCP server has 4 write tools including eth_create_nft_collection, eth_create_token, eth_generate_contract. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach PortalMCP.

How many tools does the Portal MCP server expose? +

17 tools across 4 categories: Execute, Financial, Read, Write. 4 are read-only. 13 can modify, create, or delete data.

How do I enforce a policy on PortalMCP? +

Register the Portal MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every PortalMCP tool call.

Deterministic rules across all 17 PortalMCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Instant setup, no code required.

17 PortalMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.