import_robot_output_xml · RobotWS MCP Server MCP

WHAT IT DOES

What import_robot_output_xml does on RobotWS MCP Server

AI agents use import_robot_output_xml to create or update resources in RobotWS MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your RobotWS MCP Server environment.

WHY IT NEEDS A POLICY

Why import_robot_output_xml needs a policy

The tool appears to ingest and store data persistibly (Write category). Without an explicit description, confidence is moderate. The operation is reversible (data can be updated or cleared), so it does not rise to Destructive. Given the server's SQLite metadata storage focus, this tool likely parses Robot output and writes records to the database.

From the tool's definition Tool name 'import_robot_output_xml' combined with server description indicating it 'stores metadata in SQLite' suggests the tool ingests Robot Framework output XML and persists parsed data to the database. The 'import' operation modifies stored state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

import_robot_output_xml Rate-limited

import_robot_output_xml stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "import_robot_output_xml": {
      "limits": [
        {
          "counter": "import_robot_output_xml_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about import_robot_output_xml

What does the import_robot_output_xml tool do? +

import_robot_output_xml. It is categorised as a Write tool in the RobotWS MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on import_robot_output_xml? +

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

What risk level is import_robot_output_xml? +

import_robot_output_xml is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit import_robot_output_xml? +

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

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

import_robot_output_xml is provided by the RobotWS MCP Server MCP server (stella555359/robotws_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.