get_runs

THE RISK

Low Risk

Why get_runs needs a policy

This tool retrieves test run data from the Qase platform without any side effects. It queries and returns information only, matching the Read category definition of retrieving or querying data with no side effects.

From the tool's definition Tool name 'get_runs' and description 'Get all test runs in a project' indicate data retrieval with no modification, deletion, or execution of external operations.

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

POLICY

How to control get_runs

PolicyLayer is an MCP gateway — it sits between your AI agents and QASE MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_runs:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_runs": {}
  }
}

get_runs is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register QASE MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More QASE MCP Server tools

Write create_case Create a new test case Write create_plan Create a new test plan Write create_project Create new project Write create_result Create test run result Write create_result_bulk Create multiple test run results in bulk Write create_shared_step Create a new shared step Write create_suite Create a new test suite Write update_case Update an existing test case

All 26 QASE MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_runs

What does the get_runs tool do? +

Get all test runs in a project. It is categorised as a Read tool in the QASE MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_runs? +

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

What risk level is get_runs? +

get_runs is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_runs? +

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

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

get_runs is provided by the QASE MCP Server MCP server (rikuson/mcp-qase). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every QASE MCP Server tool call.

Start from QASE MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →