AI agents use submit_model to create or update resources in Google OR-Tools server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Google OR-Tools server environment.
The tool creates or registers a new constraint model without directly executing computation or deleting data. It modifies the solver's state by introducing a new model definition.
From the tool's definition Tool description states 'Submit an optimization model in JSON format', which is a create/post operation that stores or registers a constraint model for processing.
Documented attack patterns abuse exactly the kind of access submit_model gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Google OR-Tools server, and nothing reaches the server without passing your rules. This is the rule we recommend for submit_model:
{
"version": "1",
"default": "deny",
"tools": {
"submit_model": {
"limits": [
{
"counter": "submit_model_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}submit_model stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Submit an optimization model in JSON format. It is categorised as a Write tool in the Google OR-Tools server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Google OR-Tools server MCP server in PolicyLayer and add a rule for submit_model: 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 Google OR-Tools server. Nothing to install.
submit_model 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 submit_model 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 submit_model. 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.
submit_model is provided by the Google OR-Tools server MCP server (jacck/mcp-ortools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Google OR-Tools server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
3 Google OR-Tools server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.