run_gwas · Gwas MCP: Risk & Policy

WHAT IT DOES

What run_gwas does on Gwas

AI agents invoke run_gwas to trigger actions in Gwas. 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_gwas needs a policy

This tool executes non-trivial statistical computations (GWAS analysis via regression) whose effects are contingent on arguments provided by an AI agent. While not destructive or write-oriented, it triggers external statistical operations that consume computational resources and produce results dependent on user-supplied inputs, fitting the Execute category.

From the tool's definition Tool description states it will 'Perform genome-wide association study using linear or logistic regression' and 'Returns summary statistics' — these are computational operations that execute statistical analysis pipelines on biological data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_gwas Rate-limited

run_gwas 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_gwas": {
      "limits": [
        {
          "counter": "run_gwas_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 Gwas, so you can run agents against it safely.

FAQ

Questions about run_gwas

What does the run_gwas tool do? +

Perform genome-wide association study using linear or logistic regression. Returns summary statistics including p-values, beta coefficients, and standard errors. It is categorised as a Execute tool in the Gwas 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_gwas? +

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

What risk level is run_gwas? +

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

Can I rate-limit run_gwas? +

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

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

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