AI agents call list_questions 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 lists existing survey questions for a given personage. It performs a query operation that does not modify, execute external operations, delete, or transfer funds. The low severity reflects that exposing survey questions poses minimal risk even if an AI agent misuses access to this data.
From the tool's definition Tool name is 'list_questions' and description states 'Read the questionary of a personage, ordered by step.' The verb 'Read' explicitly indicates data retrieval with no side effects.
Attacks that exploit this kind of access
Read the questionary of a personage, ordered by step. Includes each question. 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_questions: 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_questions 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_questions 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_questions. 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_questions 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 →