// SCAN REPORT

Remote Mcp Authless

6 tools. 4 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated: 12 Jun 2026

4 can modify or destroy data

2 read-only

6 tools total

Community server · catalogue entry verified 12/06/2026

How to control Remote Mcp Authless ↓

TOOL MAP

What Remote Mcp Authless exposes to your agents

Read (2) Write / Execute (3) Destructive / Financial (1)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Remote Mcp Authless tools

Destructive · Medium removeContractAddress This tool removes a contract address association from a user's record. Execute · High deployToken While token deployment itself is not necessarily financial (no direct fund movement), it involves executing code on a blockchain that creates a new contract. Write · High setContractAddress This is a Write operation—it creates or modifies configuration data by adding a contract address to a tracking list. Write · Medium setWallet This tool modifies user data (wallet address) but does not delete it irreversibly or move funds, so it is Write rather than Destructive or Financial.

4 of Remote Mcp Authless's 6 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Remote Mcp Authless

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

Deny destructive operations

{
  "removeContractAddress": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "setContractAddress": {
    "limits": [
      {
        "counter": "setcontractaddress_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "getContractAddresses": {
    "limits": [
      {
        "counter": "getcontractaddresses_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

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

Create a free account and register Remote Mcp Authless — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON REMOTE MCP AUTHLESS →

Free to start. No card required.

FULL CATALOGUE

All 6 Remote Mcp Authless tools

DESTRUCTIVE 1 tools

Destructive removeContractAddress Remove a contract address from the user

EXECUTE 1 tools

Execute deployToken Deploy a new token contract

WRITE 2 tools

Write setContractAddress Add a new contract address to track Write setWallet Set your Stellar wallet address

READ 2 tools

Read getContractAddresses Get all contract addresses for the user Read getWallet Get your Stellar wallet address

EXPLORE

Related servers

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

FAQ

Questions about Remote Mcp Authless

Can an AI agent delete data through the Remote Mcp Authless MCP server? +

Yes. The Remote Mcp Authless server exposes 1 destructive tools including removeContractAddress. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Remote Mcp Authless? +

The Remote Mcp Authless server has 2 write tools including setContractAddress, setWallet. 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 Remote Mcp Authless.

How many tools does the Remote Mcp Authless MCP server expose? +

6 tools across 4 categories: Destructive, Execute, Read, Write. 2 are read-only. 4 can modify, create, or delete data.

How do I enforce a policy on Remote Mcp Authless? +

Register the Remote Mcp Authless 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 Remote Mcp Authless tool call.

Deterministic rules across all 6 Remote Mcp Authless tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON REMOTE MCP AUTHLESS →

Free to start. No card required.

6 Remote Mcp Authless tools catalogued and risk-classified — across an index of 43,000+ MCP servers.