pr_reset_coordination

Reset/clear the current coordination run. Uses interactive elicitation for confirmation when supported, falls back to confirm=true parameter.

Server Pr Review thebtf/pr-review-mcp
Category Destructive
Risk class Critical
Parameters 00 required

What pr_reset_coordination does on Pr Review

AI agents call pr_reset_coordination to permanently remove resources in Pr Review — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why pr_reset_coordination needs a policy

Resetting/clearing a coordination run removes or overwrites existing coordination state that cannot be recovered. In the context of a PR review control plane, this destroys in-progress review coordination metadata. While not data deletion in the traditional sense, it irreversibly nullifies active coordination state, making it Destructive rather than Write.

From the tool's definition Tool name explicitly contains 'reset' and description states 'clear the current coordination run' — both indicate irreversible removal of state/data. The fallback to a confirm parameter suggests the operation cannot be easily undone.

Questions about pr_reset_coordination

What does the pr_reset_coordination tool do? +

Reset/clear the current coordination run. Uses interactive elicitation for confirmation when supported, falls back to confirm=true parameter. It is categorised as a Destructive tool in the Pr Review MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on pr_reset_coordination? +

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

What risk level is pr_reset_coordination? +

pr_reset_coordination is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit pr_reset_coordination? +

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

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

pr_reset_coordination is provided by the Pr Review MCP server (thebtf/pr-review-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.