AI agents call get_solution to retrieve information from Google OR-Tools server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool queries and returns solution data from a constraint solver without side effects. It is a retrieval operation analogous to fetching cached results. There is minimal risk of misuse since it only accesses existing solution objects and does not execute code, modify problem parameters, or delete resources.
From the tool's definition 'Get the current solution if available' - this tool retrieves an already-computed solution without modifying state, triggering new computations, or deleting data.
Documented attack patterns abuse exactly the kind of access get_solution 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 get_solution:
{
"version": "1",
"default": "deny",
"tools": {
"get_solution": {}
}
}get_solution is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get the current solution if available. It is categorised as a Read tool in the Google OR-Tools server MCP Server, which means it retrieves data without modifying state.
Register the Google OR-Tools server MCP server in PolicyLayer and add a rule for get_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 Google OR-Tools server. Nothing to install.
get_solution is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_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 get_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.
get_solution 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.