submit-test-results · QA Studio MCP Server MCP

WHAT IT DOES

What submit-test-results does on QA Studio MCP Server

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

WHY IT NEEDS A POLICY

Why submit-test-results needs a policy

This tool writes/creates new test result data in a reversible manner (test results can typically be updated or deleted by authorized users). It does not execute arbitrary code, delete data irreversibly, or involve financial transactions. While it modifies platform state, the impact is limited to QA/test management records within the QA Studio system, making it Write rather than Execute or higher severity.

From the tool's definition Tool name 'submit-test-results' and description 'Submit test results for a test run' indicate the tool creates or modifies test result records in the QA Studio platform.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

submit-test-results Rate-limited

submit-test-results 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": {
    "submit-test-results": {
      "limits": [
        {
          "counter": "submit-test-results_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 QA Studio MCP Server, so you can run agents against it safely.

FAQ

Questions about submit-test-results

What does the submit-test-results tool do? +

Submit test results for a test run (useful for manual test execution tracking). It is categorised as a Write tool in the QA Studio 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 submit-test-results? +

Register the QA Studio MCP Server MCP server in PolicyLayer and add a rule for submit-test-results: 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 QA Studio MCP Server. Nothing to install.

What risk level is submit-test-results? +

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

Can I rate-limit submit-test-results? +

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

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

submit-test-results is provided by the QA Studio MCP Server MCP server (qastudio-dev/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.