consent_window_status

A read tool on the Kiln MCP server.

SERVERKiln SOURCEcodeofaxel/Kiln

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What consent_window_status does on Kiln

AI agents call consent_window_status to retrieve information from Kiln without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why consent_window_status is rated Low

Likely queries printer window status; no side effects evident without description.

From the tool's definition uninformative description

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs consent_window_status 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 consent_window_status, this is the rule to start with:

consent_window_status Allowed

consent_window_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "consent_window_status": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about consent_window_status

What does the consent_window_status tool do? +

consent_window_status is a read tool on the Kiln MCP server. It is categorised as a Read tool in the Kiln MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on consent_window_status? +

Register the Kiln MCP server in PolicyLayer and add a rule for consent_window_status: 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 consent_window_status? +

consent_window_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit consent_window_status? +

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

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

consent_window_status 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 →

Across the catalogue

editor_status on 010 Editor → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →