Define comprehensive evaluation pipeline with multiple tools and success criteria
AI agents use workflow.create_evaluation_suite to create or update resources in ContextForge MCP Gateway — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ContextForge MCP Gateway environment.
This tool creates a new evaluation pipeline definition, which is a Write operation (creating structured configuration data). It does not appear to execute code directly or delete data.
From the tool's definition 'Define comprehensive evaluation pipeline with multiple tools and success criteria' — creates/defines a new evaluation suite configuration
Attacks that exploit this kind of access
Define comprehensive evaluation pipeline with multiple tools and success criteria. It is categorised as a Write tool in the ContextForge MCP Gateway MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ContextForge MCP Gateway MCP server in PolicyLayer and add a rule for workflow.create_evaluation_suite: 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 ContextForge MCP Gateway. Nothing to install.
workflow.create_evaluation_suite 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 workflow.create_evaluation_suite 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 workflow.create_evaluation_suite. 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.
workflow.create_evaluation_suite is provided by the ContextForge MCP Gateway MCP server (jrmatherly/mcp-context-forge). 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 →