Process a natural language request using Ollama and execute the resulting Unity commands.
AI agents invoke process_user_request to trigger actions in Unity MCP with Ollama Integration. 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 processes arbitrary natural language input and executes Unity commands based on Ollama's interpretation. This is Execute-category because it triggers external operations (Unity Editor control, asset manipulation, workflow automation) whose effects depend directly on the user request and the LLM's interpretation of it.
From the tool's definition Tool description states it will 'execute the resulting Unity commands' based on natural language processing.
Documented attack patterns abuse exactly the kind of access process_user_request gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Unity MCP with Ollama Integration, and nothing reaches the server without passing your rules. This is the rule we recommend for process_user_request:
{
"version": "1",
"default": "deny",
"tools": {
"process_user_request": {
"limits": [
{
"counter": "process_user_request_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}process_user_request stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Process a natural language request using Ollama and execute the resulting Unity commands. It is categorised as a Execute tool in the Unity MCP with Ollama Integration MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Unity MCP with Ollama Integration MCP server in PolicyLayer and add a rule for process_user_request: 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 Unity MCP with Ollama Integration. Nothing to install.
process_user_request 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 process_user_request 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 process_user_request. 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.
process_user_request is provided by the Unity MCP with Ollama Integration MCP server (zundamonnovrchatkaisetu/unity-mcp-ollama). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Unity MCP with Ollama Integration, 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.
37 Unity MCP with Ollama Integration tools catalogued and risk-classified — across an index of 43,000+ MCP servers.