Add a new solution to the current generation of the evolutionary system. Use this tool to contribute solutions to the current generation. Solutions can be: - Initial solutions (generation 0) - Evolved solutions based on crossover recommendations - Variations or mutations of existing solutions The...
AI agents use add_solution to create or update resources in Event Horizon MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Event Horizon MCP Server environment.
The tool creates or adds new data entries (solutions) to the evolutionary system in a reversible manner. It does not delete, execute arbitrary code, move funds, or trigger external operations with unpredictable side effects.
From the tool's definition Tool description states "Add a new solution to the current generation" and "Evolved solutions based on crossover recommendations" - these are create/modify operations that persist data to the evolutionary system's generation state.
Attacks that exploit this kind of access
Add a new solution to the current generation of the evolutionary system. Use this tool to contribute solutions to the current generation. Solutions can be: - Initial solutions (generation 0) - Evolved solutions based on crossover recommendations - Variations or mutations of existing solutions The solution content should directly address the problem statement. It is categorised as a Write tool in the Event Horizon MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Event Horizon MCP Server MCP server in PolicyLayer and add a rule for add_solution: 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 Event Horizon MCP Server. Nothing to install.
add_solution 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 add_solution 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 add_solution. 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.
add_solution is provided by the Event Horizon MCP Server MCP server (manasp21/eventhorizon). 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 →