This record as markdown: /tools/minhoyoo-iotrust-waiaas/wc-status.md
What wc_status does on Waiaas
AI agents call wc_status to retrieve information from Waiaas without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why wc_status is rated Low
The 'wc_status' tool appears to check wallet or connection status (probable 'wc' = wallet connect). Status queries are read-only operations that retrieve information without modifying state or executing transactions. Even in the context of a crypto wallet MCP server, a status check would simply return current state rather than perform financial transactions or execute operations.
From the tool's definition Tool name 'wc_status' suggests a status query operation. The description is empty, providing no explicit functionality details. Based on naming convention, 'status' typically indicates retrieval of state information with no side effects.
Attacks that exploit this kind of access
The rule that runs wc_status safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Waiaas, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For wc_status, this is the rule to start with:
wc_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Waiaas, apply this rule, and every wc_status call is checked against it from then on.
Questions about wc_status
wc_status is a read tool on the Waiaas MCP server. It is categorised as a Read tool in the Waiaas MCP Server, which means it retrieves data without modifying state.
Register the Waiaas MCP server in PolicyLayer and add a rule for wc_status: 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_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the wc_status 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_status. 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_status 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.
More on Waiaas, and thousands of servers like it.
This server
Across the catalogue