启动逐步模式的专家PK会话（轮次对话）
AI agents invoke start_stepwise_pk_session to trigger actions in Guru Pk. 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 initiates and controls an AI expert debate system with dynamic expert generation. Starting a session triggers dependent operations (expert generation, round management, dialogue orchestration) whose effects depend on arguments. This constitutes Execute category behavior—triggering complex external operations whose outcomes depend on input parameters.
From the tool's definition Tool name 'start_stepwise_pk_session' and description indicating it 'starts' or 'initiates' an expert PK session with round-based dialogue.
Documented attack patterns abuse exactly the kind of access start_stepwise_pk_session gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Guru Pk, and nothing reaches the server without passing your rules. This is the rule we recommend for start_stepwise_pk_session:
{
"version": "1",
"default": "deny",
"tools": {
"start_stepwise_pk_session": {
"limits": [
{
"counter": "start_stepwise_pk_session_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}start_stepwise_pk_session 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.
启动逐步模式的专家PK会话（轮次对话）. It is categorised as a Execute tool in the Guru Pk MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Guru Pk MCP server in PolicyLayer and add a rule for start_stepwise_pk_session: 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 Guru Pk. Nothing to install.
start_stepwise_pk_session 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 start_stepwise_pk_session 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 start_stepwise_pk_session. 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.
start_stepwise_pk_session is provided by the Guru Pk MCP server (mitsudoai/guru-pk-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Guru Pk, 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.
22 Guru Pk tools catalogued and risk-classified — across an index of 43,000+ MCP servers.