run_contract_scan · RWA Pipe MCP Server MCP: Risk & Policy

WHAT IT DOES

What run_contract_scan does on RWA Pipe MCP Server

AI agents invoke run_contract_scan to trigger actions in RWA Pipe MCP Server. 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.

WHY IT NEEDS A POLICY

Why run_contract_scan needs a policy

This tool executes a scanning operation on smart contracts across multiple blockchain networks. While it does not modify data (Write), delete data (Destructive), or move funds (Financial), it does trigger an external computational process whose exact impact depends on user-supplied arguments (contract address, chain selection).

From the tool's definition Tool name 'run_contract_scan' with description 'Trigger a contract scan' indicates it initiates an external operation/process across multiple blockchains.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_contract_scan Rate-limited

run_contract_scan 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": {
    "run_contract_scan": {
      "limits": [
        {
          "counter": "run_contract_scan_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches RWA Pipe MCP Server, so you can run agents against it safely.

FAQ

Questions about run_contract_scan

What does the run_contract_scan tool do? +

Trigger a contract scan for a specific asset. Supports EVM, Solana, Stellar, XRPL, Tron, Aptos, Sui, Hedera, Algorand, TON, NEAR, and Noble. Requires JWT. It is categorised as a Execute tool in the RWA Pipe MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_contract_scan? +

Register the RWA Pipe MCP Server MCP server in PolicyLayer and add a rule for run_contract_scan: 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 RWA Pipe MCP Server. Nothing to install.

What risk level is run_contract_scan? +

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

Can I rate-limit run_contract_scan? +

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

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

run_contract_scan is provided by the RWA Pipe MCP Server MCP server (rwapipe/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.