AI agents use bulk_create_review_questions to create or update resources in Leafeep — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Leafeep environment.
This tool creates new quiz review questions in bulk, modifying the review pool state. It falls into the Write category because it creates data structures (questions with statements, answers, and tags) that persist in the system.
From the tool's definition Tool description states 'Bulk create OX review questions' — the verb 'create' indicates data is being created and persisted in the review pool. This is a reversible modification (questions can be deleted or edited), not a destructive action.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Bulk create OX review questions for the review pool. Each question needs a statement, correctAnswer (true/false), and tags (from ConceptTag). It is categorised as a Write tool in the Leafeep MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Leafeep MCP server in PolicyLayer and add a rule for bulk_create_review_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 Leafeep. Nothing to install.
bulk_create_review_questions 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 bulk_create_review_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 bulk_create_review_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.
bulk_create_review_questions is provided by the Leafeep MCP server (xhae123/leafeep-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 →