connect_info

THE RISK

Low Risk

Why connect_info needs a policy

This tool only retrieves configuration and environment information (wallets, policies, capabilities). It has no side effects and does not modify any state. It is a pure read/query operation with low blast radius.

From the tool's definition Get self-discovery info: accessible wallets, policies, capabilities, and AI-ready prompt. Call this first to understand your environment.

Documented attack patterns abuse exactly the kind of access connect_info gives an agent:

POLICY

How to control connect_info

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "connect_info": {}
  }
}

connect_info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

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

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Waiaas tools

Financial dex_swap Execute DEX swap via D Financial execute_action Execute a DeFi action (swap, bridge, stake, unstake, lend_supply, lend_borrow, lend_repay, Financial aave_withdraw Withdraw supplied collateral from Aave V3 lending pool. Use amount= Financial drift_withdraw_margin Withdraw excess collateral from Drift V2 margin account to wallet Financial hl_sub_transfer Transfer USDC between master account and sub-account Financial hl_transfer_usdc Transfer USDC between Spot and Perp accounts on Hyperliquid Financial kamino_withdraw Withdraw supplied collateral from Kamino K-Lend. Use amount= Financial transfer_nft transfer_nft

All 126 Waiaas tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about connect_info

What does the connect_info tool do? +

Get self-discovery info: accessible wallets, policies, capabilities, and AI-ready prompt. Call this first to understand your environment. It is categorised as a Read tool in the Waiaas MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on connect_info? +

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

What risk level is connect_info? +

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

Can I rate-limit connect_info? +

Yes. Add a rate_limit block to the connect_info 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 connect_info completely? +

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

connect_info is provided by the Waiaas MCP server (minhoyoo-iotrust/waiaas). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Waiaas tool call.

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

CHECK YOUR STACK →