High Risk →

request_validation

Request on-chain validation for an agent via Validation Registry

How to control request_validation ↓

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.

High Risk

Why request_validation needs a policy

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

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

How to control request_validation

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

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

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.

  1. Create a free account and register Waiaas — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

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.

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.

Free to start. No card required.

126 Waiaas tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.