request_validation

Request on-chain validation for an agent via Validation Registry

SERVERWaiaas SOURCEminhoyoo-iotrust/waiaas

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/minhoyoo-iotrust-waiaas/request-validation.md

WHAT IT DOES

What request_validation does on Waiaas

AI agents invoke request_validation to trigger actions in Waiaas. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why request_validation is rated High

This tool triggers an on-chain operation (submitting a validation request to a smart contract registry), which constitutes executing an external blockchain transaction. While it is not directly moving funds, on-chain transactions have irreversible effects and may incur gas costs or alter contract state.

From the tool's definition Request on-chain validation for an agent via Validation Registry

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs request_validation 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 request_validation, this is the rule to start with:

request_validation Rate-limited

request_validation stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "request_validation": {
      "limits": [
        {
          "counter": "request_validation_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Waiaas, apply this rule, and every request_validation call is checked against it from then on.

FAQ

Questions about request_validation

What does the request_validation tool do? +

Request on-chain validation for an agent via Validation Registry. It is categorised as a Execute tool in the Waiaas MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on request_validation? +

Register the Waiaas MCP server in PolicyLayer and add a rule for request_validation: 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 request_validation? +

request_validation is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit request_validation? +

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

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

request_validation 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.

KEEP EXPLORING

More on Waiaas, and thousands of servers like it.

This server

All 126 Waiaas tools → High-risk tools on this server →

Across the catalogue

http_request on 0sec → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →