AI agents call wc_connect as a supporting operation in Waiaas workflows.
The description is empty, which significantly lowers confidence. Based on context, 'wc_connect' likely establishes a WalletConnect session (a connection/pairing operation), which is primarily a Write/Execute action setting up a communication channel. However, initiating wallet connections could enable subsequent financial operations.
From the tool's definition Tool name is 'wc_connect' with an empty description. In the context of a crypto wallet MCP server, 'wc' likely refers to WalletConnect, which is a protocol for connecting wallets to dApps.
Documented attack patterns abuse exactly the kind of access wc_connect gives an agent:
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 wc_connect:
{
"version": "1",
"default": "deny",
"tools": {
"wc_connect": {
"limits": [
{
"counter": "wc_connect_rate",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
}
} wc_connect gets a rate cap, and everything else on the server is denied unless you say otherwise.
Free to start. No card required.
wc_connect. It is categorised as a Other tool in the Waiaas MCP Server, which means it performs auxiliary operations.
Register the Waiaas MCP server in PolicyLayer and add a rule for wc_connect: 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.
wc_connect is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the wc_connect 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.
Set action: deny in the PolicyLayer policy for wc_connect. 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.
wc_connect 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.
Start from Waiaas, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
126 Waiaas tools catalogued and risk-classified — across an index of 43,000+ MCP servers.