chaoxing_delete_question_bank_question_type
Preview or confirm deleting a question type when the current UI permits it.
This record as markdown: /tools/chaoxing-agent/chaoxing-delete-question-bank-question-type.md
What chaoxing_delete_question_bank_question_type does on Chaoxing Agent
AI agents call chaoxing_delete_question_bank_question_type to permanently remove resources in Chaoxing Agent, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why chaoxing_delete_question_bank_question_type is rated Critical
An AI agent that decides to call chaoxing_delete_question_bank_question_type doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Chaoxing Agent is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs chaoxing_delete_question_bank_question_type safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Chaoxing Agent, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For chaoxing_delete_question_bank_question_type, this is the rule to start with:
chaoxing_delete_question_bank_question_type is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Chaoxing Agent, apply this rule, and every chaoxing_delete_question_bank_question_type call is checked against it from then on.
Questions about chaoxing_delete_question_bank_question_type
Preview or confirm deleting a question type when the current UI permits it. It is categorised as a Destructive tool in the Chaoxing Agent MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Chaoxing Agent MCP server in PolicyLayer and add a rule for chaoxing_delete_question_bank_question_type: 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 Chaoxing Agent. Nothing to install.
chaoxing_delete_question_bank_question_type is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the chaoxing_delete_question_bank_question_type 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 chaoxing_delete_question_bank_question_type. 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.
chaoxing_delete_question_bank_question_type is provided by the Chaoxing Agent MCP server (Cr-GH0/chaoxing-agent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Chaoxing Agent, and thousands of servers like it.
Across the catalogue