Remove an answer option from a choice-style question.
AI agents call delete_question_option to permanently remove resources in Yanifend — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes data (an answer option) that cannot be restored without re-creation. While the blast radius is limited to questionary configuration rather than user responses or financial data, it is still a destructive operation that modifies survey structure and could invalidate collected responses.
From the tool's definition Tool name 'delete_question_option' and description 'Remove an answer option from a choice-style question' explicitly indicate irreversible deletion of questionary configuration data.
Attacks that exploit this kind of access
Remove an answer option from a choice-style question. It is categorised as a Destructive tool in the Yanifend MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Yanifend MCP server in PolicyLayer and add a rule for delete_question_option: 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 Yanifend. Nothing to install.
delete_question_option 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 delete_question_option 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 delete_question_option. 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.
delete_question_option is provided by the Yanifend MCP server (skippedaga/yanifend-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →