AI agents use generate_qa_dataset to create or update resources in RAGScore — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your RAGScore environment.
Creates new datasets which are reversible writes to the system's data store. Not destructive (can be regenerated), not execute (no arbitrary code/commands), not read-only (modifies state). Medium severity because a malicious actor could generate large volumes of poor-quality data to pollute the evaluation system or waste resources, but impacts are recoverable.
From the tool's definition Tool named 'generate_qa_dataset' with empty description; based on name and sibling tools (evaluate_rag, get_corrections, quick_test_rag) on a RAG evaluation server, this tool creates new QA datasets.
Attacks that exploit this kind of access
generate_qa_dataset. It is categorised as a Write tool in the RAGScore MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the RAGScore MCP server in PolicyLayer and add a rule for generate_qa_dataset: 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 RAGScore. Nothing to install.
generate_qa_dataset 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 generate_qa_dataset 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 generate_qa_dataset. 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.
generate_qa_dataset is provided by the RAGScore MCP server (pypi:ragscore). 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 →