run_xml_verification · Prosuite MCP: Risk & Policy

WHAT IT DOES

What run_xml_verification does on Prosuite

AI agents invoke run_xml_verification to trigger actions in Prosuite. 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_xml_verification needs a policy

This tool executes verification processes against XML input, which constitutes triggering an external operation whose effects depend on the structure and content of the XML provided.

From the tool's definition Tool name 'run_xml_verification' indicates execution of verification logic against XML data. The server context shows it exposes 'quality verification' operations on geospatial datasets.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_xml_verification Rate-limited

run_xml_verification 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_xml_verification": {
      "limits": [
        {
          "counter": "run_xml_verification_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 Prosuite, so you can run agents against it safely.

FAQ

Questions about run_xml_verification

What does the run_xml_verification tool do? +

run_xml_verification. It is categorised as a Execute tool in the Prosuite 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_xml_verification? +

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

What risk level is run_xml_verification? +

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

Can I rate-limit run_xml_verification? +

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

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

run_xml_verification is provided by the Prosuite MCP server (prosuite/prosuite-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

run_xml_verification is one line of Prosuite's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →