status
Check Across bridge deposit status (filled/pending/expired/refunded)
This record as markdown: /tools/minhoyoo-iotrust-waiaas/status.md
What status does on Waiaas
AI agents call 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 status is rated Low
This tool retrieves status information about an existing bridge deposit without modifying, executing, or deleting any data. It is a pure read operation that provides visibility into transaction state. No financial risk, no code execution, no destructive action. The tool name 'status' and description both indicate a query-only operation.
From the tool's definition Check Across bridge deposit status (filled/pending/expired/refunded) — queries status of a bridge transaction with no side effects or modifications.
Attacks that exploit this kind of access
The rule that runs 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 status, this is the rule to start with:
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 status call is checked against it from then on.
Questions about status
Check Across bridge deposit status (filled/pending/expired/refunded). 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 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.
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 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 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.
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