Triggers a RAG evaluation run against a specified dataset.
AI agents invoke trigger_rag_evaluation_run to trigger actions in SDOF Knowledge Base. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes an external process (RAG evaluation) rather than merely reading or writing data. While the operation is not destructive, it causes side effects by running a computational workflow.
From the tool's definition The tool description states it 'Triggers a RAG evaluation run' — the verb 'triggers' indicates initiation of an external operation (a RAG evaluation pipeline) whose effects depend on which dataset is specified as an argument.
Attacks that exploit this kind of access
Triggers a RAG evaluation run against a specified dataset. It is categorised as a Execute tool in the SDOF Knowledge Base MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the SDOF Knowledge Base MCP server in PolicyLayer and add a rule for trigger_rag_evaluation_run: 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 SDOF Knowledge Base. Nothing to install.
trigger_rag_evaluation_run is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the trigger_rag_evaluation_run 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 trigger_rag_evaluation_run. 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.
trigger_rag_evaluation_run is provided by the SDOF Knowledge Base MCP server (tgf-between-your-legs/sdof-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 →