revoke_consent_window

A destructive tool on the Kiln MCP server.

SERVERKiln SOURCEcodeofaxel/Kiln

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/kiln/revoke-consent-window.md

WHAT IT DOES

What revoke_consent_window does on Kiln

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

RISK

Why revoke_consent_window is rated Critical

An AI agent that decides to call revoke_consent_window doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Kiln is gone. There is no undo for destructive operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs revoke_consent_window safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Kiln, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For revoke_consent_window, this is the rule to start with:

revoke_consent_window Hidden

revoke_consent_window is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "revoke_consent_window"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Kiln, apply this rule, and every revoke_consent_window call is checked against it from then on.

FAQ

Questions about revoke_consent_window

What does the revoke_consent_window tool do? +

revoke_consent_window is a destructive tool on the Kiln MCP server. It is categorised as a Destructive tool in the Kiln 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 revoke_consent_window? +

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

What risk level is revoke_consent_window? +

revoke_consent_window 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 revoke_consent_window? +

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

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

revoke_consent_window is provided by the Kiln MCP server (codeofaxel/Kiln). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Kiln, and thousands of servers like it.

This server

All 416 Kiln tools → Critical-risk tools on this server →

Across the catalogue

revoke_api_token on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →