// MCP TOOL REFERENCE

executeTests

ServerOctomind
CategoryExecute

WHAT IT DOES

What executeTests does on Octomind

AI agents invoke executeTests to trigger actions in Octomind. 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.

THE RISK

High Risk

Why executeTests needs a policy

This tool executes automated tests against a provided URL, which constitutes triggering external operations. The outcome and side effects depend entirely on what tests are executed and against which URL, making it an Execute category tool.

From the tool's definition executeTests tool 'can trigger a set of tests for a given test target' and 'tests are executed on the provided url' — this triggers external operations (test execution) whose effects depend on arguments (test target, URL, context).

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

POLICY

How to control executeTests

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "executeTests": {
      "limits": [
        {
          "counter": "executetests_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

executeTests 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.

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

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Octomind tools

Destructive deleteEnvironment deleteEnvironment tool can delete an environment for a given test target. The environm Destructive deleteTestTarget the deleteTestTarget tool can delete an existing test target. This operation cannot be Write discovery the discovery tool can create a test case on a given test target with a test case descript Write createBatchGeneration create a batch discovery for a given test target. Useful to generate multiple test cases f Write createEnvironment the createEnvironment tool can create an environment for a given test target. an envir Write createFromTestPlan create test cases from a test plan for a given test target. Provide freeform text, related Write createTestTarget the createTestTarget tool can create a new test target or project. A test target repre Write updateEnvironment the updateEnvironment tool can update an environment for a given test target. An envir

All 21 Octomind tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in Octomind → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about executeTests

What does the executeTests tool do? +

the executeTests tool can trigger a set of tests for a given test target. The test target id is unique to the test target. The tests are executed on the provided url. The context object is used to provide information about the source of the test execution. It is categorised as a Execute tool in the Octomind MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on executeTests? +

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

What risk level is executeTests? +

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

Can I rate-limit executeTests? +

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

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

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

Enforce policy on every Octomind tool call.

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

CHECK YOUR STACK →

Free to start. No card required.

21 Octomind tools catalogued and risk-classified — across an index of 43,000+ MCP servers.