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 Pointsyeah. 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 triggers execution of an external operation (a Proctor exam) whose effects depend on runtime and configuration arguments. While it appears to be a testing/validation tool rather than arbitrary code execution, it still qualifies as Execute because it runs an external process/operation whose behavior and side effects are determined by the supplied arguments.
From the tool's definition Tool name 'run_exam' and description 'Execute a Proctor exam' explicitly states it executes/runs an exam against an MCP server with 'provided runtime and MCP configuration'.
Attacks that exploit this kind of access
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 Pointsyeah MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Pointsyeah 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 Pointsyeah. 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 Pointsyeah MCP server (slack-workspace-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →