Execute a Proctor exam against an MCP server. Runs the specified exam using the provided runtime and MCP configuration. The exam tests the MCP server
AI agents invoke run_exam to trigger actions in Playwright Stealth. 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.
This tool executes an exam process (a form of automated testing/validation) against an MCP server using runtime and configuration parameters. While the exact side effects depend on what the exam does, the fundamental action is triggering code execution on a target server. This fits the Execute category—an action that runs code or triggers external operations whose effects are argument-dependent.
From the tool's definition Tool name is 'run_exam' and description states 'Execute a Proctor exam against an MCP server' and 'runs the specified exam using the provided runtime and MCP configuration'. The verb 'Execute' and 'runs' indicate code/process execution.
Documented attack patterns abuse exactly the kind of access run_exam gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Playwright Stealth, and nothing reaches the server without passing your rules. This is the rule we recommend for run_exam:
{
"version": "1",
"default": "deny",
"tools": {
"run_exam": {
"limits": [
{
"counter": "run_exam_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} run_exam 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.
Free to start. No card required.
Execute a Proctor exam against an MCP server. Runs the specified exam using the provided runtime and MCP configuration. The exam tests the MCP server. It is categorised as a Execute tool in the Playwright Stealth MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Playwright Stealth MCP server in PolicyLayer and add a rule for run_exam: 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 Playwright Stealth. Nothing to install.
run_exam is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the run_exam 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.
Set action: deny in the PolicyLayer policy for run_exam. 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.
run_exam is provided by the Playwright Stealth MCP server (pulsemcp/mcp-servers). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Playwright Stealth, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
68 Playwright Stealth tools catalogued and risk-classified — across an index of 43,000+ MCP servers.