AI agents call list_question_options to retrieve information from Yanifend without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays existing question options in a specified order. It performs a query operation only, returning data without creating, modifying, deleting, or executing any external operations. The blast radius of misuse is minimal—an agent could only enumerate available options, posing no security or operational risk.
From the tool's definition Tool name 'list_question_options' and description 'List the answer options of a choice-style question, in render order' indicate a pure retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
List the answer options of a choice-style question, in render order. It is categorised as a Read tool in the Yanifend MCP Server, which means it retrieves data without modifying state.
Register the Yanifend MCP server in PolicyLayer and add a rule for list_question_options: 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.
list_question_options is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_question_options 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 list_question_options. 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.
list_question_options 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 →