AI agents use create_question to create or update resources in Yanifend — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Yanifend environment.
This tool creates new questions within a questionary/feedback widget, modifying data in a reversible manner. It does not delete data (Destructive), execute arbitrary code (Execute), involve financial transactions (Financial), or merely read data (Read). Write category is appropriate because the action can be undone by deleting the question.
From the tool's definition Tool description states 'Add a new question to a personage', which is a create operation that modifies questionary data reversibly. The server description confirms it manages 'create/update/delete questions and options'.
Attacks that exploit this kind of access
Add a new question to a personage. It is categorised as a Write tool in the Yanifend MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Yanifend MCP server in PolicyLayer and add a rule for create_question: 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.
create_question is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_question 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 create_question. 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.
create_question 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 →